Network storage backup using distributed media agents

ABSTRACT

Certain embodiments disclosed herein reduce or eliminate a communication bottleneck at the storage manager by reducing communication with the storage manager while maintaining functionality of an information management system. In some implementations, a client obtains information for enabling a secondary storage job (e.g., a backup or restore) from a storage manager and stores the information (which may be referred to as job metadata) in a local cache. The client may then reuse the job metadata for multiple storage jobs reducing the frequency of communication with the storage manager. When a configuration of the information management system changes, or the availability of resources changes, the storage manager can push updates to the job metadata to the clients. Further, a client can periodically request updated job metadata from the storage manager ensuring that the client does not rely on out-of-date job metadata.

INCORPORATION BY REFERENCE TO ANY PRIORITY APPLICATIONS

Any and all applications, if any, for which a foreign or domesticpriority claim is identified in the Application Data Sheet of thepresent application are hereby incorporated by reference under 37 CFR1.57.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentand/or the patent disclosure as it appears in the United States Patentand Trademark Office patent file and/or records, but otherwise reservesall copyrights whatsoever.

BACKGROUND

Businesses recognize the commercial value of their data and seekreliable, cost-effective ways to protect the information stored on theircomputer networks while minimizing impact on productivity. A companymight back up critical computing systems such as databases, fileservers, web servers, virtual machines, and so on as part of a daily,weekly, or monthly maintenance schedule. The company may similarlyprotect computing systems used by its employees, such as those used byan accounting department, marketing department, engineering department,and so forth. Given the rapidly expanding volume of data undermanagement, companies also continue to seek innovative techniques formanaging data growth, for example by migrating data to lower-coststorage over time, reducing redundant data, pruning lower priority data,etc. Enterprises also increasingly view their stored data as a valuableasset and look for solutions that leverage their data. For instance,data analysis capabilities, information management, improved datapresentation and access features, and the like, are in increasingdemand.

SUMMARY

In some cases, a bottleneck may be created in an information managementsystem by components or systems of the information management systemthat help regulate the processing of data across the informationmanagement system. As the number of client devices supported by theinformation management system increases, the bottleneck can worsen,which can reduce the availability of computing resources within aninformation management system. This reduction in resource availabilitycan include a reduction in hardware processor availability and/orstorage availability. In some cases, it is not possible to scale thenumber of supported client devices to a desired level or amount becauseof the constraint on available resources at the information managementsystem.

One example where users may notice the reduction in resourceavailability due to communication bottlenecks in the informationmanagement system is in the backup or restore context. A storage managermay trigger a backup process for a client, such as a laptop. Each timethe backup process is to be performed, the storage manager will alertthe client and provide metadata to the client that, among otherfeatures, instructs the client regarding the availability of resourcesto perform the backup process. The client may then communicate data forbackup to a media agent along with metadata to facilitate indexing thedata at a backup location, such as a network storage site or a secondarystorage disk. Further, the storage manager may provide metadata to themedia agent instructing the media agent regarding resources to use tocomplete the backup, the type of backup to perform, and other backuprelated features or decisions. When the information management systemincludes a large number of clients (such as 10,000, 20,000, 100,000, or200,000 clients), the communication with the storage manager during thebackup process can cause a bottleneck in the backup process when a largenumber or percentage of the clients are to be backed up simultaneouslyor substantially in parallel. Similar problems may occur in the restorecontext.

Certain embodiments disclosed herein reduce or eliminate the bottleneckby reducing communication with the storage manager. In someimplementations, a client obtains information for enabling a secondarystorage job (e.g., a backup or restore) from a storage manager andstores the information (which may be referred to as job metadata) in alocal cache. The client may then reuse the job metadata for multiplestorage jobs reducing the frequency of communication with the storagemanager. When a configuration of the information management systemchanges, or the availability of resources changes, the storage managercan push updates to the job metadata to the clients. Further, a clientcan periodically request updated job metadata from the storage managerensuring that the client does not rely on out-of-date job metadata.

Further, certain embodiments disclosed herein enable a client of theinformation management system to communicate data directly with a cloudor network storage system while providing index data or backup metadatato the media agent. Advantageously, in certain embodiments, byseparating the data and the backup metadata, the burden on computingresources of the media agent can be reduced. In certain embodiments, bydistributing backup management, at least in part, to the client systems,communications with the storage manager and the media agent duringbackup and restore operations can be reduced. Further, the distributedbackup management enables the information management system to be scaledto support a greater number of client devices while utilizing the sameamount or fewer computing resources compared to non-distributed backupmanagement systems.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram illustrating an exemplary informationmanagement system.

FIG. 1B is a detailed view of a primary storage device, a secondarystorage device, and some examples of primary data and secondary copydata.

FIG. 1C is a block diagram of an exemplary information management systemincluding a storage manager, one or more data agents, and one or moremedia agents.

FIG. 1D is a block diagram illustrating a scalable informationmanagement system.

FIG. 1E illustrates certain secondary copy operations according to anexemplary storage policy.

FIGS. 1F-1H are block diagrams illustrating suitable data structuresthat may be employed by the information management system.

FIG. 2A illustrates a system and technique for synchronizing primarydata to a destination such as a failover site using secondary copy data.

FIG. 2B illustrates an information management system architectureincorporating use of a network file system (NFS) protocol forcommunicating between the primary and secondary storage subsystems.

FIG. 2C is a block diagram of an example of a highly scalable manageddata pool architecture.

FIG. 3 presents one example of a dataflow diagram illustrating the flowof data and metadata within an information management system.

FIG. 4 presents an alternative example of a dataflow diagramillustrating the flow of data and metadata within an informationmanagement system that reduces overhead compared to the dataflow of FIG.3 enabling an increase in scale for the information management system.

FIG. 5A is a block diagram illustrating some salient portions of asystem 500 for reducing a management burden on a storage managerenabling an increase in scale of clients supported by an informationmanagement system, according to an illustrative embodiment of thepresent invention.

FIG. 5B is a block diagram illustrating some salient portions of asystem 575 for reducing a management burden on a storage managerenabling an increase in scale of clients supported by an informationmanagement system, according to an illustrative embodiment of thepresent invention.

FIG. 6 depicts some salient operations of a client managed job process600 according to an illustrative embodiment of the present invention.

FIG. 7 depicts some salient operations of a job metadata update process700 according to an illustrative embodiment of the present invention.

FIG. 8 depicts some salient operations of a backup process 800 accordingto an illustrative embodiment of the present invention.

FIG. 9 depicts some salient operations of an indexing process 900according to an illustrative embodiment of the present invention.

FIG. 10 depicts some salient operations of a media agent restorationprocess 1000 according to an illustrative embodiment of the presentinvention.

DETAILED DESCRIPTION

Detailed descriptions and examples of systems and methods according toone or more illustrative embodiments of the present invention may befound in the section entitled Distributed Backup Management, as well asin the section entitled Example Embodiments, and also in FIGS. 3-10herein. Furthermore, components and functionality for distributingbackup management may be configured and/or incorporated into informationmanagement systems such as those described herein in FIGS. 1A-1H and2A-2C.

Various embodiments described herein are intimately tied to, enabled by,and would not exist except for, computer technology. For example,distributing backup management as described herein in reference tovarious embodiments cannot reasonably be performed by humans alone,without the computer technology upon which they are implemented.

Information Management System Overview

With the increasing importance of protecting and leveraging data,organizations simply cannot risk losing critical data. Moreover, runawaydata growth and other modern realities make protecting and managing dataincreasingly difficult. There is therefore a need for efficient,powerful, and user-friendly solutions for protecting and managing dataand for smart and efficient management of data storage. Depending on thesize of the organization, there may be many data production sourceswhich are under the purview of tens, hundreds, or even thousands ofindividuals. In the past, individuals were sometimes responsible formanaging and protecting their own data, and a patchwork of hardware andsoftware point solutions may have been used in any given organization.These solutions were often provided by different vendors and had limitedor no interoperability. Certain embodiments described herein addressthese and other shortcomings of prior approaches by implementingscalable, unified, organization-wide information management, includingdata storage management.

FIG. 1A shows one such information management system 100 (or “system100”), which generally includes combinations of hardware and softwareconfigured to protect and manage data and metadata that are generatedand used by computing devices in system 100. System 100 may be referredto in some embodiments as a “storage management system” or a “datastorage management system.” System 100 performs information managementoperations, some of which may be referred to as “storage operations” or“data storage operations,” to protect and manage the data residing inand/or managed by system 100. The organization that employs system 100may be a corporation or other business entity, non-profit organization,educational institution, household, governmental agency, or the like.

Generally, the systems and associated components described herein may becompatible with and/or provide some or all of the functionality of thesystems and corresponding components described in one or more of thefollowing U.S. patents/publications and patent applications assigned toCommvault Systems, Inc., each of which is hereby incorporated byreference in its entirety herein:

-   -   U.S. Pat. No. 7,035,880, entitled “Modular Backup and Retrieval        System Used in Conjunction With a Storage Area Network”;    -   U.S. Pat. No. 7,107,298, entitled “System And Method For        Archiving Objects In An Information Store”;    -   U.S. Pat. No. 7,246,207, entitled “System and Method for        Dynamically Performing Storage Operations in a Computer        Network”;    -   U.S. Pat. No. 7,315,923, entitled “System And Method For        Combining Data Streams In Pipelined Storage Operations In A        Storage Network”;    -   U.S. Pat. No. 7,343,453, entitled “Hierarchical Systems and        Methods for Providing a Unified View of Storage Information”;    -   U.S. Pat. No. 7,395,282, entitled “Hierarchical Backup and        Retrieval System”;    -   U.S. Pat. No. 7,529,782, entitled “System and Methods for        Performing a Snapshot and for Restoring Data”;    -   U.S. Pat. No. 7,617,262, entitled “System and Methods for        Monitoring Application Data in a Data Replication System”;    -   U.S. Pat. No. 7,734,669, entitled “Managing Copies Of Data”;    -   U.S. Pat. No. 7,747,579, entitled “Metabase for Facilitating        Data Classification”;    -   U.S. Pat. No. 8,156,086, entitled “Systems And Methods For        Stored Data Verification”;    -   U.S. Pat. No. 8,170,995, entitled “Method and System for Offline        Indexing of Content and Classifying Stored Data”;    -   U.S. Pat. No. 8,230,195, entitled “System And Method For        Performing Auxiliary Storage Operations”;    -   U.S. Pat. No. 8,285,681, entitled “Data Object Store and Server        for a Cloud Storage Environment, Including Data Deduplication        and Data Management Across Multiple Cloud Storage Sites”;    -   U.S. Pat. No. 8,307,177, entitled “Systems And Methods For        Management Of Virtualization Data”;    -   U.S. Pat. No. 8,364,652, entitled “Content-Aligned, Block-Based        Deduplication”;    -   U.S. Pat. No. 8,578,120, entitled “Block-Level Single        Instancing”;    -   U.S. Pat. No. 8,954,446, entitled “Client-Side Repository in a        Networked Deduplicated Storage System”;    -   U.S. Pat. No. 9,020,900, entitled “Distributed Deduplicated        Storage System”;    -   U.S. Pat. No. 9,098,495, entitled “Application-Aware and Remote        Single Instance Data Management”;    -   U.S. Pat. No. 9,239,687, entitled “Systems and Methods for        Retaining and Using Data Block Signatures in Data Protection        Operations”;    -   U.S. Pat. Pub. No. 2006/0224846, entitled “System and Method to        Support Single Instance Storage Operations”;    -   U.S. Pat. Pub. No. 2014/0201170, entitled “High Availability        Distributed Deduplicated Storage System”;    -   U.S. patent application Ser. No. 14/721,971, entitled        “Replication Using Deduplicated Secondary Copy Data” (applicant        docket no. 100.422.US1.145; attorney docket no. COMMV.252A);    -   U.S. Patent Application No. 62/265,339 entitled “Live        Synchronization and Management of Virtual Machines across        Computing and Virtualization Platforms and Using Live        Synchronization to Support Disaster Recovery” (applicant docket        no. 100.487.USP1.160; attorney docket no. COMMV.277PR);    -   U.S. Patent Application No. 62/273,286 entitled “Redundant and        Robust Distributed Deduplication Data Storage System” (applicant        docket no. 100.489.USP1.135; attorney docket no. COMMV.279PR);    -   U.S. Patent Application No. 62/294,920, entitled “Data        Protection Operations Based on Network Path Information”        (applicant docket no. 100.497.USP1.105; attorney docket no.        COMMV.283PR);    -   U.S. Patent Application No. 62/297,057, entitled “Data        Restoration Operations Based on Network Path Information”        (applicant docket no. 100.498.USP1.105; attorney docket no.        COMMV.284PR); and    -   U.S. Patent Application No. 62/387,384, entitled        “Application-Level Live Synchronization Across Computing        Platforms Including Synchronizing Co-Resident Applications To        Disparate Standby Destinations And Selectively Synchronizing        Some Applications And Not Others” (applicant docket no.        100.500.USP1.105; attorney docket no. COMMV.286PR).

System 100 includes computing devices and computing technologies. Forinstance, system 100 can include one or more client computing devices102 and secondary storage computing devices 106, as well as storagemanager 140 or a host computing device for it. Computing devices caninclude, without limitation, one or more: workstations, personalcomputers, desktop computers, or other types of generally fixedcomputing systems such as mainframe computers, servers, andminicomputers. Other computing devices can include mobile or portablecomputing devices, such as one or more laptops, tablet computers,personal data assistants, mobile phones (such as smartphones), and othermobile or portable computing devices such as embedded computers, set topboxes, vehicle-mounted devices, wearable computers, etc. Servers caninclude mail servers, file servers, database servers, virtual machineservers, and web servers. Any given computing device comprises one ormore processors (e.g., CPU and/or single-core or multi-core processors),as well as corresponding non-transitory computer memory (e.g.,random-access memory (RAM)) for storing computer programs which are tobe executed by the one or more processors. Other computer memory formass storage of data may be packaged/configured with the computingdevice (e.g., an internal hard disk) and/or may be external andaccessible by the computing device (e.g., network-attached storage, astorage array, etc.). In some cases, a computing device includes cloudcomputing resources, which may be implemented as virtual machines. Forinstance, one or more virtual machines may be provided to theorganization by a third-party cloud service vendor.

In some embodiments, computing devices can include one or more virtualmachine(s) running on a physical host computing device (or “hostmachine”) operated by the organization. As one example, the organizationmay use one virtual machine as a database server and another virtualmachine as a mail server, both virtual machines operating on the samehost machine. A Virtual machine (“VM”) is a software implementation of acomputer that does not physically exist and is instead instantiated inan operating system of a physical computer (or host machine) to enableapplications to execute within the VM's environment, i.e., a VM emulatesa physical computer. A VM includes an operating system and associatedvirtual resources, such as computer memory and processor(s). Ahypervisor operates between the VM and the hardware of the physical hostmachine and is generally responsible for creating and running the VMs.Hypervisors are also known in the art as virtual machine monitors or avirtual machine managers or “VMMs”, and may be implemented in software,firmware, and/or specialized hardware installed on the host machine.Examples of hypervisors include ESX Server, by VMware, Inc. of PaloAlto, Calif.; Microsoft Virtual Server and Microsoft Windows ServerHyper-V, both by Microsoft Corporation of Redmond, Wash.; Sun xVM byOracle America Inc. of Santa Clara, Calif.; and Xen by Citrix Systems,Santa Clara, Calif. The hypervisor provides resources to each virtualoperating system such as a virtual processor, virtual memory, a virtualnetwork device, and a virtual disk. Each virtual machine has one or moreassociated virtual disks. The hypervisor typically stores the data ofvirtual disks in files on the file system of the physical host machine,called virtual machine disk files (“VMDK” in VMware lingo) or virtualhard disk image files (in Microsoft lingo). For example, VMware's ESXServer provides the Virtual Machine File System (VMFS) for the storageof virtual machine disk files. A virtual machine reads data from andwrites data to its virtual disk much the way that a physical machinereads data from and writes data to a physical disk. Examples oftechniques for implementing information management in a cloud computingenvironment are described in U.S. Pat. No. 8,285,681. Examples oftechniques for implementing information management in a virtualizedcomputing environment are described in U.S. Pat. No. 8,307,177.

Information management system 100 can also include electronic datastorage devices, generally used for mass storage of data, including,e.g., primary storage devices 104 and secondary storage devices 108.Storage devices can generally be of any suitable type including, withoutlimitation, disk drives, storage arrays (e.g., storage-area network(SAN) and/or network-attached storage (NAS) technology), semiconductormemory (e.g., solid state storage devices), network attached storage(NAS) devices, tape libraries, or other magnetic, non-tape storagedevices, optical media storage devices, DNA/RNA-based memory technology,combinations of the same, etc. In some embodiments, storage devices formpart of a distributed file system. In some cases, storage devices areprovided in a cloud storage environment (e.g., a private cloud or oneoperated by a third-party vendor), whether for primary data or secondarycopies or both.

Depending on context, the term “information management system” can referto generally all of the illustrated hardware and software components inFIG. 1C, or the term may refer to only a subset of the illustratedcomponents. For instance, in some cases, system 100 generally refers toa combination of specialized components used to protect, move, manage,manipulate, analyze, and/or process data and metadata generated byclient computing devices 102. However, system 100 in some cases does notinclude the underlying components that generate and/or store primarydata 112, such as the client computing devices 102 themselves, and theprimary storage devices 104. Likewise secondary storage devices 108(e.g., a third-party provided cloud storage environment) may not be partof system 100. As an example, “information management system” or“storage management system” may sometimes refer to one or more of thefollowing components, which will be described in further detail below:storage manager, data agent, and media agent.

One or more client computing devices 102 may be part of system 100, eachclient computing device 102 having an operating system and at least oneapplication 110 and one or more accompanying data agents executingthereon; and associated with one or more primary storage devices 104storing primary data 112. Client computing device(s) 102 and primarystorage devices 104 may generally be referred to in some cases asprimary storage subsystem 117.

Client Computing Devices, Clients, and Subclients

Typically, a variety of sources in an organization produce data to beprotected and managed. As just one illustrative example, in a corporateenvironment such data sources can be employee workstations and companyservers such as a mail server, a web server, a database server, atransaction server, or the like. In system 100, data generation sourcesinclude one or more client computing devices 102. A computing devicethat has a data agent 142 installed and operating on it is generallyreferred to as a “client computing device” 102, and may include any typeof computing device, without limitation. A client computing device 102may be associated with one or more users and/or user accounts.

A “client” is a logical component of information management system 100,which may represent a logical grouping of one or more data agentsinstalled on a client computing device 102. Storage manager 140recognizes a client as a component of system 100, and in someembodiments, may automatically create a client component the first timea data agent 142 is installed on a client computing device 102. Becausedata generated by executable component(s) 110 is tracked by theassociated data agent 142 so that it may be properly protected in system100, a client may be said to generate data and to store the generateddata to primary storage, such as primary storage device 104. However,the terms “client” and “client computing device” as used herein do notimply that a client computing device 102 is necessarily configured inthe client/server sense relative to another computing device such as amail server, or that a client computing device 102 cannot be a server inits own right. As just a few examples, a client computing device 102 canbe and/or include mail servers, file servers, database servers, virtualmachine servers, and/or web servers.

Each client computing device 102 may have application(s) 110 executingthereon which generate and manipulate the data that is to be protectedfrom loss and managed in system 100. Applications 110 generallyfacilitate the operations of an organization, and can include, withoutlimitation, mail server applications (e.g., Microsoft Exchange Server),file system applications, mail client applications (e.g., MicrosoftExchange Client), database applications or database management systems(e.g., SQL, Oracle, SAP, Lotus Notes Database), word processingapplications (e.g., Microsoft Word), spreadsheet applications, financialapplications, presentation applications, graphics and/or videoapplications, browser applications, mobile applications, entertainmentapplications, and so on. Each application 110 may be accompanied by anapplication-specific data agent 142, though not all data agents 142 areapplication-specific or associated with only application. A file system,e.g., Microsoft Windows Explorer, may be considered an application 110and may be accompanied by its own data agent 142. Client computingdevices 102 can have at least one operating system (e.g., MicrosoftWindows, Mac OS X, iOS, IBM z/OS, Linux, other Unix-based operatingsystems, etc.) installed thereon, which may support or host one or morefile systems and other applications 110. In some embodiments, a virtualmachine that executes on a host client computing device 102 may beconsidered an application 110 and may be accompanied by a specific dataagent 142 (e.g., virtual server data agent).

Client computing devices 102 and other components in system 100 can beconnected to one another via one or more electronic communicationpathways 114. For example, a first communication pathway 114 maycommunicatively couple client computing device 102 and secondary storagecomputing device 106; a second communication pathway 114 maycommunicatively couple storage manager 140 and client computing device102; and a third communication pathway 114 may communicatively couplestorage manager 140 and secondary storage computing device 106, etc.(see, e.g., FIG. 1A and FIG. 1C). A communication pathway 114 caninclude one or more networks or other connection types including one ormore of the following, without limitation: the Internet, a wide areanetwork (WAN), a local area network (LAN), a Storage Area Network (SAN),a Fibre Channel (FC) connection, a Small Computer System Interface(SCSI) connection, a virtual private network (VPN), a token ring orTCP/IP based network, an intranet network, a point-to-point link, acellular network, a wireless data transmission system, a two-way cablesystem, an interactive kiosk network, a satellite network, a broadbandnetwork, a baseband network, a neural network, a mesh network, an ad hocnetwork, other appropriate computer or telecommunications networks,combinations of the same or the like. Communication pathways 114 in somecases may also include application programming interfaces (APIs)including, e.g., cloud service provider APIs, virtual machine managementAPIs, and hosted service provider APIs. The underlying infrastructure ofcommunication pathways 114 may be wired and/or wireless, analog and/ordigital, or any combination thereof; and the facilities used may beprivate, public, third-party provided, or any combination thereof,without limitation.

A “subclient” is a logical grouping of all or part of a client's primarydata 112. In general, a subclient may be defined according to how thesubclient data is to be protected as a unit in system 100. For example,a subclient may be associated with a certain storage policy. A givenclient may thus comprise several subclients, each subclient associatedwith a different storage policy. For example, some files may form afirst subclient that requires compression and deduplication and isassociated with a first storage policy. Other files of the client mayform a second subclient that requires a different retention schedule aswell as encryption, and may be associated with a different, secondstorage policy. As a result, though the primary data may be generated bythe same application 110 and may belong to one given client, portions ofthe data may be assigned to different subclients for distinct treatmentby system 100. More detail on subclients is given in regard to storagepolicies below.

Primary Data and Exemplary Primary Storage Devices

Primary data 112 is generally production data or “live” data generatedby the operating system and/or applications 110 executing on clientcomputing device 102. Primary data 112 is generally stored on primarystorage device(s) 104 and is organized via a file system operating onthe client computing device 102. Thus, client computing device(s) 102and corresponding applications 110 may create, access, modify, write,delete, and otherwise use primary data 112. Primary data 112 isgenerally in the native format of the source application 110. Primarydata 112 is an initial or first stored body of data generated by thesource application 110. Primary data 112 in some cases is createdsubstantially directly from data generated by the corresponding sourceapplication 110. It can be useful in performing certain tasks toorganize primary data 112 into units of different granularities. Ingeneral, primary data 112 can include files, directories, file systemvolumes, data blocks, extents, or any other hierarchies or organizationsof data objects. As used herein, a “data object” can refer to (i) anyfile that is currently addressable by a file system or that waspreviously addressable by the file system (e.g., an archive file),and/or to (ii) a subset of such a file (e.g., a data block, an extent,etc.). Primary data 112 may include structured data (e.g., databasefiles), unstructured data (e.g., documents), and/or semi-structureddata. See, e.g., FIG. 1B.

It can also be useful in performing certain functions of system 100 toaccess and modify metadata within primary data 112. Metadata generallyincludes information about data objects and/or characteristicsassociated with the data objects. For simplicity herein, it is to beunderstood that, unless expressly stated otherwise, any reference toprimary data 112 generally also includes its associated metadata, butreferences to metadata generally do not include the primary data.Metadata can include, without limitation, one or more of the following:the data owner (e.g., the client or user that generates the data), thelast modified time (e.g., the time of the most recent modification ofthe data object), a data object name (e.g., a file name), a data objectsize (e.g., a number of bytes of data), information about the content(e.g., an indication as to the existence of a particular search term),user-supplied tags, to/from information for email (e.g., an emailsender, recipient, etc.), creation date, file type (e.g., format orapplication type), last accessed time, application type (e.g., type ofapplication that generated the data object), location/network (e.g., acurrent, past or future location of the data object and network pathwaysto/from the data object), geographic location (e.g., GPS coordinates),frequency of change (e.g., a period in which the data object ismodified), business unit (e.g., a group or department that generates,manages or is otherwise associated with the data object), aginginformation (e.g., a schedule, such as a time period, in which the dataobject is migrated to secondary or long term storage), boot sectors,partition layouts, file location within a file folder directorystructure, user permissions, owners, groups, access control lists(ACLs), system metadata (e.g., registry information), combinations ofthe same or other similar information related to the data object. Inaddition to metadata generated by or related to file systems andoperating systems, some applications 110 and/or other components ofsystem 100 maintain indices of metadata for data objects, e.g., metadataassociated with individual email messages. The use of metadata toperform classification and other functions is described in greaterdetail below.

Primary storage devices 104 storing primary data 112 may be relativelyfast and/or expensive technology (e.g., flash storage, a disk drive, ahard-disk storage array, solid state memory, etc.), typically to supporthigh-performance live production environments. Primary data 112 may behighly changeable and/or may be intended for relatively short termretention (e.g., hours, days, or weeks). According to some embodiments,client computing device 102 can access primary data 112 stored inprimary storage device 104 by making conventional file system calls viathe operating system. Each client computing device 102 is generallyassociated with and/or in communication with one or more primary storagedevices 104 storing corresponding primary data 112. A client computingdevice 102 is said to be associated with or in communication with aparticular primary storage device 104 if it is capable of one or moreof: routing and/or storing data (e.g., primary data 112) to the primarystorage device 104, coordinating the routing and/or storing of data tothe primary storage device 104, retrieving data from the primary storagedevice 104, coordinating the retrieval of data from the primary storagedevice 104, and modifying and/or deleting data in the primary storagedevice 104. Thus, a client computing device 102 may be said to accessdata stored in an associated storage device 104.

Primary storage device 104 may be dedicated or shared. In some cases,each primary storage device 104 is dedicated to an associated clientcomputing device 102, e.g., a local disk drive. In other cases, one ormore primary storage devices 104 can be shared by multiple clientcomputing devices 102, e.g., via a local network, in a cloud storageimplementation, etc. As one example, primary storage device 104 can be astorage array shared by a group of client computing devices 102, such asEMC Clariion, EMC Symmetrix, EMC Celerra, Dell EqualLogic, IBM XIV,NetApp FAS, HP EVA, and HP 3PAR.

System 100 may also include hosted services (not shown), which may behosted in some cases by an entity other than the organization thatemploys the other components of system 100. For instance, the hostedservices may be provided by online service providers. Such serviceproviders can provide social networking services, hosted email services,or hosted productivity applications or other hosted applications such assoftware-as-a-service (SaaS), platform-as-a-service (PaaS), applicationservice providers (ASPs), cloud services, or other mechanisms fordelivering functionality via a network. As it services users, eachhosted service may generate additional data and metadata, which may bemanaged by system 100, e.g., as primary data 112. In some cases, thehosted services may be accessed using one of the applications 110. As anexample, a hosted mail service may be accessed via browser running on aclient computing device 102.

Secondary Copies and Exemplary Secondary Storage Devices

Primary data 112 stored on primary storage devices 104 may becompromised in some cases, such as when an employee deliberately oraccidentally deletes or overwrites primary data 112. Or primary storagedevices 104 can be damaged, lost, or otherwise corrupted. For recoveryand/or regulatory compliance purposes, it is therefore useful togenerate and maintain copies of primary data 112. Accordingly, system100 includes one or more secondary storage computing devices 106 and oneor more secondary storage devices 108 configured to create and store oneor more secondary copies 116 of primary data 112 including itsassociated metadata. The secondary storage computing devices 106 and thesecondary storage devices 108 may be referred to as secondary storagesubsystem 118.

Secondary copies 116 can help in search and analysis efforts and meetother information management goals as well, such as: restoring dataand/or metadata if an original version is lost (e.g., by deletion,corruption, or disaster); allowing point-in-time recovery; complyingwith regulatory data retention and electronic discovery (e-discovery)requirements; reducing utilized storage capacity in the productionsystem and/or in secondary storage; facilitating organization and searchof data; improving user access to data files across multiple computingdevices and/or hosted services; and implementing data retention andpruning policies.

A secondary copy 116 can comprise a separate stored copy of data that isderived from one or more earlier-created stored copies (e.g., derivedfrom primary data 112 or from another secondary copy 116). Secondarycopies 116 can include point-in-time data, and may be intended forrelatively long-term retention before some or all of the data is movedto other storage or discarded. In some cases, a secondary copy 116 maybe in a different storage device than other previously stored copies;and/or may be remote from other previously stored copies. Secondarycopies 116 can be stored in the same storage device as primary data 112.For example, a disk array capable of performing hardware snapshotsstores primary data 112 and creates and stores hardware snapshots of theprimary data 112 as secondary copies 116. Secondary copies 116 may bestored in relatively slow and/or lower cost storage (e.g., magnetictape). A secondary copy 116 may be stored in a backup or archive format,or in some other format different from the native source applicationformat or other format of primary data 112.

Secondary storage computing devices 106 may index secondary copies 116(e.g., using a media agent 144), enabling users to browse and restore ata later time and further enabling the lifecycle management of theindexed data. After creation of a secondary copy 116 that representscertain primary data 112, a pointer or other location indicia (e.g., astub) may be placed in primary data 112, or be otherwise associated withprimary data 112, to indicate the current location of a particularsecondary copy 116. Since an instance of a data object or metadata inprimary data 112 may change over time as it is modified by application110 (or hosted service or the operating system), system 100 may createand manage multiple secondary copies 116 of a particular data object ormetadata, each copy representing the state of the data object in primarydata 112 at a particular point in time. Moreover, since an instance of adata object in primary data 112 may eventually be deleted from primarystorage device 104 and the file system, system 100 may continue tomanage point-in-time representations of that data object, even thoughthe instance in primary data 112 no longer exists. For virtual machines,the operating system and other applications 110 of client computingdevice(s) 102 may execute within or under the management ofvirtualization software (e.g., a VMM), and the primary storage device(s)104 may comprise a virtual disk created on a physical storage device.System 100 may create secondary copies 116 of the files or other dataobjects in a virtual disk file and/or secondary copies 116 of the entirevirtual disk file itself (e.g., of an entire .vmdk file).

Secondary copies 116 are distinguishable from corresponding primary data112. First, secondary copies 116 can be stored in a different formatfrom primary data 112 (e.g., backup, archive, or other non-nativeformat). For this or other reasons, secondary copies 116 may not bedirectly usable by applications 110 or client computing device 102(e.g., via standard system calls or otherwise) without modification,processing, or other intervention by system 100 which may be referred toas “restore” operations. Secondary copies 116 may have been processed bydata agent 142 and/or media agent 144 in the course of being created(e.g., compression, deduplication, encryption, integrity markers,indexing, formatting, application-aware metadata, etc.), and thussecondary copy 116 may represent source primary data 112 withoutnecessarily being exactly identical to the source.

Second, secondary copies 116 may be stored on a secondary storage device108 that is inaccessible to application 110 running on client computingdevice 102 and/or hosted service. Some secondary copies 116 may be“offline copies,” in that they are not readily available (e.g., notmounted to tape or disk). Offline copies can include copies of data thatsystem 100 can access without human intervention (e.g., tapes within anautomated tape library, but not yet mounted in a drive), and copies thatthe system 100 can access only with some human intervention (e.g., tapeslocated at an offsite storage site).

Using Intermediate Devices for Creating Secondary Copies—SecondaryStorage Computing Devices

Creating secondary copies can be challenging when hundreds or thousandsof client computing devices 102 continually generate large volumes ofprimary data 112 to be protected. Also, there can be significantoverhead involved in the creation of secondary copies 116. Moreover,specialized programmed intelligence and/or hardware capability isgenerally needed for accessing and interacting with secondary storagedevices 108. Client computing devices 102 may interact directly with asecondary storage device 108 to create secondary copies 116, but in viewof the factors described above, this approach can negatively impact theability of client computing device 102 to serve/service application 110and produce primary data 112. Further, any given client computing device102 may not be optimized for interaction with certain secondary storagedevices 108.

Thus, system 100 may include one or more software and/or hardwarecomponents which generally act as intermediaries between clientcomputing devices 102 (that generate primary data 112) and secondarystorage devices 108 (that store secondary copies 116). In addition tooff-loading certain responsibilities from client computing devices 102,these intermediate components provide other benefits. For instance, asdiscussed further below with respect to FIG. 1D, distributing some ofthe work involved in creating secondary copies 116 can enhancescalability and improve system performance. For instance, usingspecialized secondary storage computing devices 106 and media agents 144for interfacing with secondary storage devices 108 and/or for performingcertain data processing operations can greatly improve the speed withwhich system 100 performs information management operations and can alsoimprove the capacity of the system to handle large numbers of suchoperations, while reducing the computational load on the productionenvironment of client computing devices 102. The intermediate componentscan include one or more secondary storage computing devices 106 as shownin FIG. 1A and/or one or more media agents 144. Media agents arediscussed further below (e.g., with respect to FIGS. 1C-1E). Thesespecial-purpose components of system 100 comprise specialized programmedintelligence and/or hardware capability for writing to, reading from,instructing, communicating with, or otherwise interacting with secondarystorage devices 108.

Secondary storage computing device(s) 106 can comprise any of thecomputing devices described above, without limitation. In some cases,secondary storage computing device(s) 106 also include specializedhardware componentry and/or software intelligence (e.g., specializedinterfaces) for interacting with certain secondary storage device(s) 108with which they may be specially associated.

To create a secondary copy 116 involving the copying of data fromprimary storage subsystem 117 to secondary storage subsystem 118, clientcomputing device 102 may communicate the primary data 112 to be copied(or a processed version thereof generated by a data agent 142) to thedesignated secondary storage computing device 106, via a communicationpathway 114. Secondary storage computing device 106 in turn may furtherprocess and convey the data or a processed version thereof to secondarystorage device 108. One or more secondary copies 116 may be created fromexisting secondary copies 116, such as in the case of an auxiliary copyoperation, described further below.

Exemplary Primary Data and an Exemplary Secondary Copy

FIG. 1B is a detailed view of some specific examples of primary datastored on primary storage device(s) 104 and secondary copy data storedon secondary storage device(s) 108, with other components of the systemremoved for the purposes of illustration. Stored on primary storagedevice(s) 104 are primary data 112 objects including word processingdocuments 119A-B, spreadsheets 120, presentation documents 122, videofiles 124, image files 126, email mailboxes 128 (and corresponding emailmessages 129A-C), HTML/XML or other types of markup language files 130,databases 132 and corresponding tables or other data structures133A-133C. Some or all primary data 112 objects are associated withcorresponding metadata (e.g., “Meta1-11”), which may include file systemmetadata and/or application-specific metadata. Stored on the secondarystorage device(s) 108 are secondary copy 116 data objects 134A-C whichmay include copies of or may otherwise represent corresponding primarydata 112.

Secondary copy data objects 134A-C can individually represent more thanone primary data object. For example, secondary copy data object 134Arepresents three separate primary data objects 133C, 122, and 129C(represented as 133C′, 122′, and 129C′, respectively, and accompanied bycorresponding metadata Meta11, Meta3, and Meta8, respectively).Moreover, as indicated by the prime mark (′), secondary storagecomputing devices 106 or other components in secondary storage subsystem118 may process the data received from primary storage subsystem 117 andstore a secondary copy including a transformed and/or supplementedrepresentation of a primary data object and/or metadata that isdifferent from the original format, e.g., in a compressed, encrypted,deduplicated, or other modified format. For instance, secondary storagecomputing devices 106 can generate new metadata or other informationbased on said processing, and store the newly generated informationalong with the secondary copies. Secondary copy data object 1346represents primary data objects 120, 1336, and 119A as 120′, 1336′, and119A′, respectively, accompanied by corresponding metadata Meta2,Meta10, and Meta1, respectively. Also, secondary copy data object 134Crepresents primary data objects 133A, 119B, and 129A as 133A′, 1196′,and 129A′, respectively, accompanied by corresponding metadata Meta9,Meta5, and Meta6, respectively.

Exemplary Information Management System Architecture

System 100 can incorporate a variety of different hardware and softwarecomponents, which can in turn be organized with respect to one anotherin many different configurations, depending on the embodiment. There arecritical design choices involved in specifying the functionalresponsibilities of the components and the role of each component insystem 100. Such design choices can impact how system 100 performs andadapts to data growth and other changing circumstances. FIG. 1C shows asystem 100 designed according to these considerations and includes:storage manager 140, one or more data agents 142 executing on clientcomputing device(s) 102 and configured to process primary data 112, andone or more media agents 144 executing on one or more secondary storagecomputing devices 106 for performing tasks involving secondary storagedevices 108.

Storage Manager

Storage manager 140 is a centralized storage and/or information managerthat is configured to perform certain control functions and also tostore certain critical information about system 100—hence storagemanager 140 is said to manage system 100. As noted, the number ofcomponents in system 100 and the amount of data under management can belarge. Managing the components and data is therefore a significant task,which can grow unpredictably as the number of components and data scaleto meet the needs of the organization. For these and other reasons,according to certain embodiments, responsibility for controlling system100, or at least a significant portion of that responsibility, isallocated to storage manager 140. Storage manager 140 can be adaptedindependently according to changing circumstances, without having toreplace or re-design the remainder of the system. Moreover, a computingdevice for hosting and/or operating as storage manager 140 can beselected to best suit the functions and networking needs of storagemanager 140. These and other advantages are described in further detailbelow and with respect to FIG. 1D.

Storage manager 140 may be a software module or other application hostedby a suitable computing device. In some embodiments, storage manager 140is itself a computing device that performs the functions describedherein. Storage manager 140 comprises or operates in conjunction withone or more associated data structures such as a dedicated database(e.g., management database 146), depending on the configuration. Thestorage manager 140 generally initiates, performs, coordinates, and/orcontrols storage and other information management operations performedby system 100, e.g., to protect and control primary data 112 andsecondary copies 116. In general, storage manager 140 is said to managesystem 100, which includes communicating with, instructing, andcontrolling in some circumstances components such as data agents 142 andmedia agents 144, etc.

As shown by the dashed arrowed lines 114 in FIG. 1C, storage manager 140may communicate with, instruct, and/or control some or all elements ofsystem 100, such as data agents 142 and media agents 144. In thismanner, storage manager 140 manages the operation of various hardwareand software components in system 100. In certain embodiments, controlinformation originates from storage manager 140 and status as well asindex reporting is transmitted to storage manager 140 by the managedcomponents, whereas payload data and metadata are generally communicatedbetween data agents 142 and media agents 144 (or otherwise betweenclient computing device(s) 102 and secondary storage computing device(s)106), e.g., at the direction of and under the management of storagemanager 140. Control information can generally include parameters andinstructions for carrying out information management operations, suchas, without limitation, instructions to perform a task associated withan operation, timing information specifying when to initiate a task,data path information specifying what components to communicate with oraccess in carrying out an operation, and the like. In other embodiments,some information management operations are controlled or initiated byother components of system 100 (e.g., by media agents 144 or data agents142), instead of or in combination with storage manager 140.

According to certain embodiments, storage manager 140 provides one ormore of the following functions:

-   -   communicating with data agents 142 and media agents 144,        including transmitting instructions, messages, and/or queries,        as well as receiving status reports, index information,        messages, and/or queries, and responding to same;    -   initiating execution of information management operations;    -   initiating restore and recovery operations;    -   managing secondary storage devices 108 and inventory/capacity of        the same;    -   allocating secondary storage devices 108 for secondary copy        operations;    -   reporting, searching, and/or classification of data in system        100;    -   monitoring completion of and status reporting related to        information management operations and jobs;    -   tracking movement of data within system 100;    -   tracking age information relating to secondary copies 116,        secondary storage devices 108, comparing the age information        against retention guidelines, and initiating data pruning when        appropriate;    -   tracking logical associations between components in system 100;    -   protecting metadata associated with system 100, e.g., in        management database 146;    -   implementing job management, schedule management, event        management, alert management, reporting, job history        maintenance, user security management, disaster recovery        management, and/or user interfacing for system administrators        and/or end users of system 100;    -   sending, searching, and/or viewing of log files; and    -   implementing operations management functionality.

Storage manager 140 may maintain an associated database 146 (or “storagemanager database 146” or “management database 146”) ofmanagement-related data and information management policies 148.Database 146 is stored in computer memory accessible by storage manager140. Database 146 may include a management index 150 (or “index 150”) orother data structure(s) that may store: logical associations betweencomponents of the system; user preferences and/or profiles (e.g.,preferences regarding encryption, compression, or deduplication ofprimary data or secondary copies; preferences regarding the scheduling,type, or other aspects of secondary copy or other operations; mappingsof particular information management users or user accounts to certaincomputing devices or other components, etc.; management tasks; mediacontainerization; other useful data; and/or any combination thereof. Forexample, storage manager 140 may use index 150 to track logicalassociations between media agents 144 and secondary storage devices 108and/or movement of data to/from secondary storage devices 108. Forinstance, index 150 may store data associating a client computing device102 with a particular media agent 144 and/or secondary storage device108, as specified in an information management policy 148.

Administrators and others may configure and initiate certain informationmanagement operations on an individual basis. But while this may beacceptable for some recovery operations or other infrequent tasks, it isoften not workable for implementing on-going organization-wide dataprotection and management. Thus, system 100 may utilize informationmanagement policies 148 for specifying and executing informationmanagement operations on an automated basis. Generally, an informationmanagement policy 148 can include a stored data structure or otherinformation source that specifies parameters (e.g., criteria and rules)associated with storage management or other information managementoperations. Storage manager 140 can process an information managementpolicy 148 and/or index 150 and, based on the results, identify aninformation management operation to perform, identify the appropriatecomponents in system 100 to be involved in the operation (e.g., clientcomputing devices 102 and corresponding data agents 142, secondarystorage computing devices 106 and corresponding media agents 144, etc.),establish connections to those components and/or between thosecomponents, and/or instruct and control those components to carry outthe operation. In this manner, system 100 can translate storedinformation into coordinated activity among the various computingdevices in system 100.

Management database 146 may maintain information management policies 148and associated data, although information management policies 148 can bestored in computer memory at any appropriate location outside managementdatabase 146. For instance, an information management policy 148 such asa storage policy may be stored as metadata in a media agent database 152or in a secondary storage device 108 (e.g., as an archive copy) for usein restore or other information management operations, depending on theembodiment. Information management policies 148 are described furtherbelow. According to certain embodiments, management database 146comprises a relational database (e.g., an SQL database) for trackingmetadata, such as metadata associated with secondary copy operations(e.g., what client computing devices 102 and corresponding subclientdata were protected and where the secondary copies are stored and whichmedia agent 144 performed the storage operation(s)). This and othermetadata may additionally be stored in other locations, such as atsecondary storage computing device 106 or on the secondary storagedevice 108, allowing data recovery without the use of storage manager140 in some cases. Thus, management database 146 may comprise dataneeded to kick off secondary copy operations (e.g., storage policies,schedule policies, etc.), status and reporting information aboutcompleted jobs (e.g., status and error reports on yesterday's backupjobs), and additional information sufficient to enable restore anddisaster recovery operations (e.g., media agent associations, locationindexing, content indexing, etc.).

Storage manager 140 may include a jobs agent 156, a user interface 158,and a management agent 154, all of which may be implemented asinterconnected software modules or application programs. These aredescribed further below.

Jobs agent 156 in some embodiments initiates, controls, and/or monitorsthe status of some or all information management operations previouslyperformed, currently being performed, or scheduled to be performed bysystem 100. A job is a logical grouping of information managementoperations such as daily storage operations scheduled for a certain setof subclients (e.g., generating incremental block-level backup copies116 at a certain time every day for database files in a certaingeographical location). Thus, jobs agent 156 may access informationmanagement policies 148 (e.g., in management database 146) to determinewhen, where, and how to initiate/control jobs in system 100.

Storage Manager User Interfaces

User interface 158 may include information processing and displaysoftware, such as a graphical user interface (GUI), an applicationprogram interface (API), and/or other interactive interface(s) throughwhich users and system processes can retrieve information about thestatus of information management operations or issue instructions tostorage manager 140 and other components. Via user interface 158, usersmay issue instructions to the components in system 100 regardingperformance of secondary copy and recovery operations. For example, auser may modify a schedule concerning the number of pending secondarycopy operations. As another example, a user may employ the GUI to viewthe status of pending secondary copy jobs or to monitor the status ofcertain components in system 100 (e.g., the amount of capacity left in astorage device). Storage manager 140 may track information that permitsit to select, designate, or otherwise identify content indices,deduplication databases, or similar databases or resources or data setswithin its information management cell (or another cell) to be searchedin response to certain queries. Such queries may be entered by the userby interacting with user interface 158.

Various embodiments of information management system 100 may beconfigured and/or designed to generate user interface data usable forrendering the various interactive user interfaces described. The userinterface data may be used by system 100 and/or by another system,device, and/or software program (for example, a browser program), torender the interactive user interfaces. The interactive user interfacesmay be displayed on, for example, electronic displays (including, forexample, touch-enabled displays), consoles, etc., whetherdirect-connected to storage manager 140 or communicatively coupledremotely, e.g., via an internet connection. The present disclosuredescribes various embodiments of interactive and dynamic userinterfaces, some of which may be generated by user interface agent 158,and which are the result of significant technological development. Theuser interfaces described herein may provide improved human-computerinteractions, allowing for significant cognitive and ergonomicefficiencies and advantages over previous systems, including reducedmental workloads, improved decision-making, and the like. User interface158 may operate in a single integrated view or console (not shown). Theconsole may support a reporting capability for generating a variety ofreports, which may be tailored to a particular aspect of informationmanagement.

User interfaces are not exclusive to storage manager 140 and in someembodiments a user may access information locally from a computingdevice component of system 100. For example, some information pertainingto installed data agents 142 and associated data streams may beavailable from client computing device 102. Likewise, some informationpertaining to media agents 144 and associated data streams may beavailable from secondary storage computing device 106.

Storage Manager Management Agent

Management agent 154 can provide storage manager 140 with the ability tocommunicate with other components within system 100 and/or with otherinformation management cells via network protocols and applicationprogramming interfaces (APIs) including, e.g., HTTP, HTTPS, FTP, REST,virtualization software APIs, cloud service provider APIs, and hostedservice provider APIs, without limitation. Management agent 154 alsoallows multiple information management cells to communicate with oneanother. For example, system 100 in some cases may be one informationmanagement cell in a network of multiple cells adjacent to one anotheror otherwise logically related, e.g., in a WAN or LAN. With thisarrangement, the cells may communicate with one another throughrespective management agents 154. Inter-cell communications andhierarchy is described in greater detail in e.g., U.S. Pat. No.7,343,453.

Information Management Cell

An “information management cell” (or “storage operation cell” or “cell”)may generally include a logical and/or physical grouping of acombination of hardware and software components associated withperforming information management operations on electronic data,typically one storage manager 140 and at least one data agent 142(executing on a client computing device 102) and at least one mediaagent 144 (executing on a secondary storage computing device 106). Forinstance, the components shown in FIG. 1C may together form aninformation management cell. Thus, in some configurations, a system 100may be referred to as an information management cell or a storageoperation cell. A given cell may be identified by the identity of itsstorage manager 140, which is generally responsible for managing thecell.

Multiple cells may be organized hierarchically, so that cells mayinherit properties from hierarchically superior cells or be controlledby other cells in the hierarchy (automatically or otherwise).Alternatively, in some embodiments, cells may inherit or otherwise beassociated with information management policies, preferences,information management operational parameters, or other properties orcharacteristics according to their relative position in a hierarchy ofcells. Cells may also be organized hierarchically according to function,geography, architectural considerations, or other factors useful ordesirable in performing information management operations. For example,a first cell may represent a geographic segment of an enterprise, suchas a Chicago office, and a second cell may represent a differentgeographic segment, such as a New York City office. Other cells mayrepresent departments within a particular office, e.g., human resources,finance, engineering, etc. Where delineated by function, a first cellmay perform one or more first types of information management operations(e.g., one or more first types of secondary copies at a certainfrequency), and a second cell may perform one or more second types ofinformation management operations (e.g., one or more second types ofsecondary copies at a different frequency and under different retentionrules). In general, the hierarchical information is maintained by one ormore storage managers 140 that manage the respective cells (e.g., incorresponding management database(s) 146).

Data Agents

A variety of different applications 110 can operate on a given clientcomputing device 102, including operating systems, file systems,database applications, e-mail applications, and virtual machines, justto name a few. And, as part of the process of creating and restoringsecondary copies 116, the client computing device 102 may be tasked withprocessing and preparing the primary data 112 generated by these variousapplications 110. Moreover, the nature of the processing/preparation candiffer across application types, e.g., due to inherent structural,state, and formatting differences among applications 110 and/or theoperating system of client computing device 102. Each data agent 142 istherefore advantageously configured in some embodiments to assist in theperformance of information management operations based on the type ofdata that is being protected at a client-specific and/orapplication-specific level.

Data agent 142 is a component of information system 100 and is generallydirected by storage manager 140 to participate in creating or restoringsecondary copies 116. Data agent 142 may be a software program (e.g., inthe form of a set of executable binary files) that executes on the sameclient computing device 102 as the associated application 110 that dataagent 142 is configured to protect. Data agent 142 is generallyresponsible for managing, initiating, or otherwise assisting in theperformance of information management operations in reference to itsassociated application(s) 110 and corresponding primary data 112 whichis generated/accessed by the particular application(s) 110. Forinstance, data agent 142 may take part in copying, archiving, migrating,and/or replicating of certain primary data 112 stored in the primarystorage device(s) 104. Data agent 142 may receive control informationfrom storage manager 140, such as commands to transfer copies of dataobjects and/or metadata to one or more media agents 144. Data agent 142also may compress, deduplicate, and encrypt certain primary data 112, aswell as capture application-related metadata before transmitting theprocessed data to media agent 144. Data agent 142 also may receiveinstructions from storage manager 140 to restore (or assist inrestoring) a secondary copy 116 from secondary storage device 108 toprimary storage 104, such that the restored data may be properlyaccessed by application 110 in a suitable format as though it wereprimary data 112.

Each data agent 142 may be specialized for a particular application 110.For instance, different individual data agents 142 may be designed tohandle Microsoft Exchange data, Lotus Notes data, Microsoft Windows filesystem data, Microsoft Active Directory Objects data, SQL Server data,SharePoint data, Oracle database data, SAP database data, virtualmachines and/or associated data, and other types of data. A file systemdata agent, for example, may handle data files and/or other file systeminformation. If a client computing device 102 has two or more types ofdata 112, a specialized data agent 142 may be used for each data type.For example, to backup, migrate, and/or restore all of the data on aMicrosoft Exchange server, the client computing device 102 may use: (1)a Microsoft Exchange Mailbox data agent 142 to back up the Exchangemailboxes; (2) a Microsoft Exchange Database data agent 142 to back upthe Exchange databases; (3) a Microsoft Exchange Public Folder dataagent 142 to back up the Exchange Public Folders; and (4) a MicrosoftWindows File System data agent 142 to back up the file system of clientcomputing device 102. In this example, these specialized data agents 142are treated as four separate data agents 142 even though they operate onthe same client computing device 102. Other examples may include archivemanagement data agents such as a migration archiver or a compliancearchiver, Quick Recovery® agents, and continuous data replicationagents. Application-specific data agents 142 can provide improvedperformance as compared to generic agents. For instance, becauseapplication-specific data agents 142 may only handle data for a singlesoftware application, the design, operation, and performance of the dataagent 142 can be streamlined. The data agent 142 may therefore executefaster and consume less persistent storage and/or operating memory thandata agents designed to generically accommodate multiple differentsoftware applications 110.

Each data agent 142 may be configured to access data and/or metadatastored in the primary storage device(s) 104 associated with data agent142 and its host client computing device 102, and process the dataappropriately. For example, during a secondary copy operation, dataagent 142 may arrange or assemble the data and metadata into one or morefiles having a certain format (e.g., a particular backup or archiveformat) before transferring the file(s) to a media agent 144 or othercomponent. The file(s) may include a list of files or other metadata. Insome embodiments, a data agent 142 may be distributed between clientcomputing device 102 and storage manager 140 (and any other intermediatecomponents) or may be deployed from a remote location or its functionsapproximated by a remote process that performs some or all of thefunctions of data agent 142. In addition, a data agent 142 may performsome functions provided by media agent 144. Other embodiments may employone or more generic data agents 142 that can handle and process datafrom two or more different applications 110, or that can handle andprocess multiple data types, instead of or in addition to usingspecialized data agents 142. For example, one generic data agent 142 maybe used to back up, migrate and restore Microsoft Exchange Mailbox dataand Microsoft Exchange Database data, while another generic data agentmay handle Microsoft Exchange Public Folder data and Microsoft WindowsFile System data.

Media Agents

As noted, off-loading certain responsibilities from client computingdevices 102 to intermediate components such as secondary storagecomputing device(s) 106 and corresponding media agent(s) 144 can providea number of benefits including improved performance of client computingdevice 102, faster and more reliable information management operations,and enhanced scalability. In one example which will be discussed furtherbelow, media agent 144 can act as a local cache of recently-copied dataand/or metadata stored to secondary storage device(s) 108, thusimproving restore capabilities and performance for the cached data.

Media agent 144 is a component of system 100 and is generally directedby storage manager 140 in creating and restoring secondary copies 116.Whereas storage manager 140 generally manages system 100 as a whole,media agent 144 provides a portal to certain secondary storage devices108, such as by having specialized features for communicating with andaccessing certain associated secondary storage device 108. Media agent144 may be a software program (e.g., in the form of a set of executablebinary files) that executes on a secondary storage computing device 106.Media agent 144 generally manages, coordinates, and facilitates thetransmission of data between a data agent 142 (executing on clientcomputing device 102) and secondary storage device(s) 108 associatedwith media agent 144. For instance, other components in the system mayinteract with media agent 144 to gain access to data stored onassociated secondary storage device(s) 108, (e.g., to browse, read,write, modify, delete, or restore data). Moreover, media agents 144 cangenerate and store information relating to characteristics of the storeddata and/or metadata, or can generate and store other types ofinformation that generally provides insight into the contents of thesecondary storage devices 108—generally referred to as indexing of thestored secondary copies 116. Each media agent 144 may operate on adedicated secondary storage computing device 106, while in otherembodiments a plurality of media agents 144 may operate on the samesecondary storage computing device 106.

A media agent 144 may be associated with a particular secondary storagedevice 108 if that media agent 144 is capable of one or more of: routingand/or storing data to the particular secondary storage device 108;coordinating the routing and/or storing of data to the particularsecondary storage device 108; retrieving data from the particularsecondary storage device 108; coordinating the retrieval of data fromthe particular secondary storage device 108; and modifying and/ordeleting data retrieved from the particular secondary storage device108. Media agent 144 in certain embodiments is physically separate fromthe associated secondary storage device 108. For instance, a media agent144 may operate on a secondary storage computing device 106 in adistinct housing, package, and/or location from the associated secondarystorage device 108. In one example, a media agent 144 operates on afirst server computer and is in communication with a secondary storagedevice(s) 108 operating in a separate rack-mounted RAID-based system.

A media agent 144 associated with a particular secondary storage device108 may instruct secondary storage device 108 to perform an informationmanagement task. For instance, a media agent 144 may instruct a tapelibrary to use a robotic arm or other retrieval means to load or eject acertain storage media, and to subsequently archive, migrate, or retrievedata to or from that media, e.g., for the purpose of restoring data to aclient computing device 102. As another example, a secondary storagedevice 108 may include an array of hard disk drives or solid statedrives organized in a RAID configuration, and media agent 144 mayforward a logical unit number (LUN) and other appropriate information tothe array, which uses the received information to execute the desiredsecondary copy operation. Media agent 144 may communicate with asecondary storage device 108 via a suitable communications link, such asa SCSI or Fibre Channel link.

Each media agent 144 may maintain an associated media agent database152. Media agent database 152 may be stored to a disk or other storagedevice (not shown) that is local to the secondary storage computingdevice 106 on which media agent 144 executes. In other cases, mediaagent database 152 is stored separately from the host secondary storagecomputing device 106. Media agent database 152 can include, among otherthings, a media agent index 153 (see, e.g., FIG. 1C). In some cases,media agent index 153 does not form a part of and is instead separatefrom media agent database 152.

Media agent index 153 (or “index 153”) may be a data structureassociated with the particular media agent 144 that includes informationabout the stored data associated with the particular media agent andwhich may be generated in the course of performing a secondary copyoperation or a restore. Index 153 provides a fast and efficientmechanism for locating/browsing secondary copies 116 or other datastored in secondary storage devices 108 without having to accesssecondary storage device 108 to retrieve the information from there. Forinstance, for each secondary copy 116, index 153 may include metadatasuch as a list of the data objects (e.g., files/subdirectories, databaseobjects, mailbox objects, etc.), a logical path to the secondary copy116 on the corresponding secondary storage device 108, locationinformation (e.g., offsets) indicating where the data objects are storedin the secondary storage device 108, when the data objects were createdor modified, etc. Thus, index 153 includes metadata associated with thesecondary copies 116 that is readily available for use from media agent144. In some embodiments, some or all of the information in index 153may instead or additionally be stored along with secondary copies 116 insecondary storage device 108. In some embodiments, a secondary storagedevice 108 can include sufficient information to enable a “bare metalrestore,” where the operating system and/or software applications of afailed client computing device 102 or another target may beautomatically restored without manually reinstalling individual softwarepackages (including operating systems).

Because index 153 may operate as a cache, it can also be referred to asan “index cache.” In such cases, information stored in index cache 153typically comprises data that reflects certain particulars aboutrelatively recent secondary copy operations. After some triggeringevent, such as after some time elapses or index cache 153 reaches aparticular size, certain portions of index cache 153 may be copied ormigrated to secondary storage device 108, e.g., on a least-recently-usedbasis. This information may be retrieved and uploaded back into indexcache 153 or otherwise restored to media agent 144 to facilitateretrieval of data from the secondary storage device(s) 108. In someembodiments, the cached information may include format orcontainerization information related to archives or other files storedon storage device(s) 108.

In some alternative embodiments media agent 144 generally acts as acoordinator or facilitator of secondary copy operations between clientcomputing devices 102 and secondary storage devices 108, but does notactually write the data to secondary storage device 108. For instance,storage manager 140 (or media agent 144) may instruct a client computingdevice 102 and secondary storage device 108 to communicate with oneanother directly. In such a case, client computing device 102 transmitsdata directly or via one or more intermediary components to secondarystorage device 108 according to the received instructions, and viceversa. Media agent 144 may still receive, process, and/or maintainmetadata related to the secondary copy operations, i.e., may continue tobuild and maintain index 153. In these embodiments, payload data canflow through media agent 144 for the purposes of populating index 153,but not for writing to secondary storage device 108. Media agent 144and/or other components such as storage manager 140 may in some casesincorporate additional functionality, such as data classification,content indexing, deduplication, encryption, compression, and the like.Further details regarding these and other functions are described below.

Distributed, Scalable Architecture

As described, certain functions of system 100 can be distributed amongstvarious physical and/or logical components. For instance, one or more ofstorage manager 140, data agents 142, and media agents 144 may operateon computing devices that are physically separate from one another. Thisarchitecture can provide a number of benefits. For instance, hardwareand software design choices for each distributed component can betargeted to suit its particular function. The secondary computingdevices 106 on which media agents 144 operate can be tailored forinteraction with associated secondary storage devices 108 and providefast index cache operation, among other specific tasks. Similarly,client computing device(s) 102 can be selected to effectively serviceapplications 110 in order to efficiently produce and store primary data112.

Moreover, in some cases, one or more of the individual components ofinformation management system 100 can be distributed to multipleseparate computing devices. As one example, for large file systems wherethe amount of data stored in management database 146 is relativelylarge, database 146 may be migrated to or may otherwise reside on aspecialized database server (e.g., an SQL server) separate from a serverthat implements the other functions of storage manager 140. Thisdistributed configuration can provide added protection because database146 can be protected with standard database utilities (e.g., SQL logshipping or database replication) independent from other functions ofstorage manager 140. Database 146 can be efficiently replicated to aremote site for use in the event of a disaster or other data loss at theprimary site. Or database 146 can be replicated to another computingdevice within the same site, such as to a higher performance machine inthe event that a storage manager host computing device can no longerservice the needs of a growing system 100.

The distributed architecture also provides scalability and efficientcomponent utilization. FIG. 1D shows an embodiment of informationmanagement system 100 including a plurality of client computing devices102 and associated data agents 142 as well as a plurality of secondarystorage computing devices 106 and associated media agents 144.Additional components can be added or subtracted based on the evolvingneeds of system 100. For instance, depending on where bottlenecks areidentified, administrators can add additional client computing devices102, secondary storage computing devices 106, and/or secondary storagedevices 108. Moreover, where multiple fungible components are available,load balancing can be implemented to dynamically address identifiedbottlenecks. As an example, storage manager 140 may dynamically selectwhich media agents 144 and/or secondary storage devices 108 to use forstorage operations based on a processing load analysis of media agents144 and/or secondary storage devices 108, respectively.

Where system 100 includes multiple media agents 144 (see, e.g., FIG.1D), a first media agent 144 may provide failover functionality for asecond failed media agent 144. In addition, media agents 144 can bedynamically selected to provide load balancing. Each client computingdevice 102 can communicate with, among other components, any of themedia agents 144, e.g., as directed by storage manager 140. And eachmedia agent 144 may communicate with, among other components, any ofsecondary storage devices 108, e.g., as directed by storage manager 140.Thus, operations can be routed to secondary storage devices 108 in adynamic and highly flexible manner, to provide load balancing, failover,etc. Further examples of scalable systems capable of dynamic storageoperations, load balancing, and failover are provided in U.S. Pat. No.7,246,207.

While distributing functionality amongst multiple computing devices canhave certain advantages, in other contexts it can be beneficial toconsolidate functionality on the same computing device. In alternativeconfigurations, certain components may reside and execute on the samecomputing device. As such, in other embodiments, one or more of thecomponents shown in FIG. 1C may be implemented on the same computingdevice. In one configuration, a storage manager 140, one or more dataagents 142, and/or one or more media agents 144 are all implemented onthe same computing device. In other embodiments, one or more data agents142 and one or more media agents 144 are implemented on the samecomputing device, while storage manager 140 is implemented on a separatecomputing device, etc. without limitation.

Exemplary Types of Information Management Operations, Including StorageOperations

In order to protect and leverage stored data, system 100 can beconfigured to perform a variety of information management operations,which may also be referred to in some cases as storage managementoperations or storage operations. These operations can generally include(i) data movement operations, (ii) processing and data manipulationoperations, and (iii) analysis, reporting, and management operations.

Data Movement Operations, Including Secondary Copy Operations

Data movement operations are generally storage operations that involvethe copying or migration of data between different locations in system100. For example, data movement operations can include operations inwhich stored data is copied, migrated, or otherwise transferred from oneor more first storage devices to one or more second storage devices,such as from primary storage device(s) 104 to secondary storagedevice(s) 108, from secondary storage device(s) 108 to differentsecondary storage device(s) 108, from secondary storage devices 108 toprimary storage devices 104, or from primary storage device(s) 104 todifferent primary storage device(s) 104, or in some cases within thesame primary storage device 104 such as within a storage array.

Data movement operations can include by way of example, backupoperations, archive operations, information lifecycle managementoperations such as hierarchical storage management operations,replication operations (e.g., continuous data replication), snapshotoperations, deduplication or single-instancing operations, auxiliarycopy operations, disaster-recovery copy operations, and the like. Aswill be discussed, some of these operations do not necessarily createdistinct copies. Nonetheless, some or all of these operations aregenerally referred to as “secondary copy operations” for simplicity,because they involve secondary copies. Data movement also comprisesrestoring secondary copies.

Backup Operations

A backup operation creates a copy of a version of primary data 112 at aparticular point in time (e.g., one or more files or other data units).Each subsequent backup copy 116 (which is a form of secondary copy 116)may be maintained independently of the first. A backup generallyinvolves maintaining a version of the copied primary data 112 as well asbackup copies 116. Further, a backup copy in some embodiments isgenerally stored in a form that is different from the native format,e.g., a backup format. This contrasts to the version in primary data 112which may instead be stored in a format native to the sourceapplication(s) 110. In various cases, backup copies can be stored in aformat in which the data is compressed, encrypted, deduplicated, and/orotherwise modified from the original native application format. Forexample, a backup copy may be stored in a compressed backup format thatfacilitates efficient long-term storage. Backup copies 116 can haverelatively long retention periods as compared to primary data 112, whichis generally highly changeable. Backup copies 116 may be stored on mediawith slower retrieval times than primary storage device 104. Some backupcopies may have shorter retention periods than some other types ofsecondary copies 116, such as archive copies (described below). Backupsmay be stored at an offsite location.

Backup operations can include full backups, differential backups,incremental backups, “synthetic full” backups, and/or creating a“reference copy.” A full backup (or “standard full backup”) in someembodiments is generally a complete image of the data to be protected.However, because full backup copies can consume a relatively largeamount of storage, it can be useful to use a full backup copy as abaseline and only store changes relative to the full backup copyafterwards.

A differential backup operation (or cumulative incremental backupoperation) tracks and stores changes that occurred since the last fullbackup. Differential backups can grow quickly in size, but can restorerelatively efficiently because a restore can be completed in some casesusing only the full backup copy and the latest differential copy.

An incremental backup operation generally tracks and stores changessince the most recent backup copy of any type, which can greatly reducestorage utilization. In some cases, however, restoring can be lengthycompared to full or differential backups because completing a restoreoperation may involve accessing a full backup in addition to multipleincremental backups.

Synthetic full backups generally consolidate data without directlybacking up data from the client computing device. A synthetic fullbackup is created from the most recent full backup (i.e., standard orsynthetic) and subsequent incremental and/or differential backups. Theresulting synthetic full backup is identical to what would have beencreated had the last backup for the subclient been a standard fullbackup. Unlike standard full, incremental, and differential backups,however, a synthetic full backup does not actually transfer data fromprimary storage to the backup media, because it operates as a backupconsolidator. A synthetic full backup extracts the index data of eachparticipating subclient. Using this index data and the previously backedup user data images, it builds new full backup images (e.g., bitmaps),one for each subclient. The new backup images consolidate the index anduser data stored in the related incremental, differential, and previousfull backups into a synthetic backup file that fully represents thesubclient (e.g., via pointers) but does not comprise all its constituentdata.

Any of the above types of backup operations can be at the volume level,file level, or block level. Volume level backup operations generallyinvolve copying of a data volume (e.g., a logical disk or partition) asa whole. In a file-level backup, information management system 100generally tracks changes to individual files and includes copies offiles in the backup copy. For block-level backups, files are broken intoconstituent blocks, and changes are tracked at the block level. Uponrestore, system 100 reassembles the blocks into files in a transparentfashion. Far less data may actually be transferred and copied tosecondary storage devices 108 during a file-level copy than avolume-level copy. Likewise, a block-level copy may transfer less datathan a file-level copy, resulting in faster execution. However,restoring a relatively higher-granularity copy can result in longerrestore times. For instance, when restoring a block-level copy, theprocess of locating and retrieving constituent blocks can sometimes takelonger than restoring file-level backups.

A reference copy may comprise copy(ies) of selected objects from backedup data, typically to help organize data by keeping contextualinformation from multiple sources together, and/or help retain specificdata for a longer period of time, such as for legal hold needs. Areference copy generally maintains data integrity, and when the data isrestored, it may be viewed in the same format as the source data. Insome embodiments, a reference copy is based on a specialized client,individual subclient and associated information management policies(e.g., storage policy, retention policy, etc.) that are administeredwithin system 100.

Archive Operations

Because backup operations generally involve maintaining a version of thecopied primary data 112 and also maintaining backup copies in secondarystorage device(s) 108, they can consume significant storage capacity. Toreduce storage consumption, an archive operation according to certainembodiments creates an archive copy 116 by both copying and removingsource data. Or, seen another way, archive operations can involve movingsome or all of the source data to the archive destination. Thus, datasatisfying criteria for removal (e.g., data of a threshold age or size)may be removed from source storage. The source data may be primary data112 or a secondary copy 116, depending on the situation. As with backupcopies, archive copies can be stored in a format in which the data iscompressed, encrypted, deduplicated, and/or otherwise modified from theformat of the original application or source copy. In addition, archivecopies may be retained for relatively long periods of time (e.g., years)and, in some cases are never deleted. In certain embodiments, archivecopies may be made and kept for extended periods in order to meetcompliance regulations.

Archiving can also serve the purpose of freeing up space in primarystorage device(s) 104 and easing the demand on computational resourceson client computing device 102. Similarly, when a secondary copy 116 isarchived, the archive copy can therefore serve the purpose of freeing upspace in the source secondary storage device(s) 108. Examples of dataarchiving operations are provided in U.S. Pat. No. 7,107,298.

Snapshot Operations

Snapshot operations can provide a relatively lightweight, efficientmechanism for protecting data. From an end-user viewpoint, a snapshotmay be thought of as an “instant” image of primary data 112 at a givenpoint in time, and may include state and/or status information relativeto an application 110 that creates/manages primary data 112. In oneembodiment, a snapshot may generally capture the directory structure ofan object in primary data 112 such as a file or volume or other data setat a particular moment in time and may also preserve file attributes andcontents. A snapshot in some cases is created relatively quickly, e.g.,substantially instantly, using a minimum amount of file space, but maystill function as a conventional file system backup.

A “hardware snapshot” (or “hardware-based snapshot”) operation occurswhere a target storage device (e.g., a primary storage device 104 or asecondary storage device 108) performs the snapshot operation in aself-contained fashion, substantially independently, using hardware,firmware and/or software operating on the storage device itself. Forinstance, the storage device may perform snapshot operations generallywithout intervention or oversight from any of the other components ofthe system 100, e.g., a storage array may generate an “array-created”hardware snapshot and may also manage its storage, integrity,versioning, etc. In this manner, hardware snapshots can off-load othercomponents of system 100 from snapshot processing. An array may receivea request from another component to take a snapshot and then proceed toexecute the “hardware snapshot” operations autonomously, preferablyreporting success to the requesting component.

A “software snapshot” (or “software-based snapshot”) operation, on theother hand, occurs where a component in system 100 (e.g., clientcomputing device 102, etc.) implements a software layer that manages thesnapshot operation via interaction with the target storage device. Forinstance, the component executing the snapshot management software layermay derive a set of pointers and/or data that represents the snapshot.The snapshot management software layer may then transmit the same to thetarget storage device, along with appropriate instructions for writingthe snapshot. One example of a software snapshot product is MicrosoftVolume Snapshot Service (VSS), which is part of the Microsoft Windowsoperating system.

Some types of snapshots do not actually create another physical copy ofall the data as it existed at the particular point in time, but maysimply create pointers that map files and directories to specific memorylocations (e.g., to specific disk blocks) where the data resides as itexisted at the particular point in time. For example, a snapshot copymay include a set of pointers derived from the file system or from anapplication. In some other cases, the snapshot may be created at theblock-level, such that creation of the snapshot occurs without awarenessof the file system. Each pointer points to a respective stored datablock, so that collectively, the set of pointers reflect the storagelocation and state of the data object (e.g., file(s) or volume(s) ordata set(s)) at the point in time when the snapshot copy was created.

An initial snapshot may use only a small amount of disk space needed torecord a mapping or other data structure representing or otherwisetracking the blocks that correspond to the current state of the filesystem. Additional disk space is usually required only when files anddirectories change later on. Furthermore, when files change, typicallyonly the pointers which map to blocks are copied, not the blocksthemselves. For example for “copy-on-write” snapshots, when a blockchanges in primary storage, the block is copied to secondary storage orcached in primary storage before the block is overwritten in primarystorage, and the pointer to that block is changed to reflect the newlocation of that block. The snapshot mapping of file system data mayalso be updated to reflect the changed block(s) at that particular pointin time. In some other cases, a snapshot includes a full physical copyof all or substantially all of the data represented by the snapshot.Further examples of snapshot operations are provided in U.S. Pat. No.7,529,782. A snapshot copy in many cases can be made quickly and withoutsignificantly impacting primary computing resources because largeamounts of data need not be copied or moved. In some embodiments, asnapshot may exist as a virtual file system, parallel to the actual filesystem. Users in some cases gain read-only access to the record of filesand directories of the snapshot. By electing to restore primary data 112from a snapshot taken at a given point in time, users may also returnthe current file system to the state of the file system that existedwhen the snapshot was taken.

Replication Operations

Replication is another type of secondary copy operation. Some types ofsecondary copies 116 periodically capture images of primary data 112 atparticular points in time (e.g., backups, archives, and snapshots).However, it can also be useful for recovery purposes to protect primarydata 112 in a more continuous fashion, by replicating primary data 112substantially as changes occur. In some cases a replication copy can bea mirror copy, for instance, where changes made to primary data 112 aremirrored or substantially immediately copied to another location (e.g.,to secondary storage device(s) 108). By copying each write operation tothe replication copy, two storage systems are kept synchronized orsubstantially synchronized so that they are virtually identical atapproximately the same time. Where entire disk volumes are mirrored,however, mirroring can require significant amount of storage space andutilizes a large amount of processing resources.

According to some embodiments, secondary copy operations are performedon replicated data that represents a recoverable state, or “known goodstate” of a particular application running on the source system. Forinstance, in certain embodiments, known good replication copies may beviewed as copies of primary data 112. This feature allows the system todirectly access, copy, restore, back up, or otherwise manipulate thereplication copies as if they were the “live” primary data 112. This canreduce access time, storage utilization, and impact on sourceapplications 110, among other benefits. Based on known good stateinformation, system 100 can replicate sections of application data thatrepresent a recoverable state rather than rote copying of blocks ofdata. Examples of replication operations (e.g., continuous datareplication) are provided in U.S. Pat. No. 7,617,262.

Deduplication/Single-Instancing Operations

Deduplication or single-instance storage is useful to reduce the amountof non-primary data. For instance, some or all of the above-describedsecondary copy operations can involve deduplication in some fashion. Newdata is read, broken down into data portions of a selected granularity(e.g., sub-file level blocks, files, etc.), compared with correspondingportions that are already in secondary storage, and only new/changedportions are stored. Portions that already exist are represented aspointers to the already-stored data. Thus, a deduplicated secondary copy116 may comprise actual data portions copied from primary data 112 andmay further comprise pointers to already-stored data, which is generallymore storage-efficient than a full copy.

In order to streamline the comparison process, system 100 may calculateand/or store signatures (e.g., hashes or cryptographically unique IDs)corresponding to the individual source data portions and compare thesignatures to already-stored data signatures, instead of comparingentire data portions. In some cases, only a single instance of each dataportion is stored, and deduplication operations may therefore bereferred to interchangeably as “single-instancing” operations. Dependingon the implementation, however, deduplication operations can store morethan one instance of certain data portions, yet still significantlyreduce stored-data redundancy. Depending on the embodiment,deduplication portions such as data blocks can be of fixed or variablelength. Using variable length blocks can enhance deduplication byresponding to changes in the data stream, but can involve more complexprocessing. In some cases, system 100 utilizes a technique fordynamically aligning deduplication blocks based on changing content inthe data stream, as described in U.S. Pat. No. 8,364,652.

System 100 can deduplicate in a variety of manners at a variety oflocations. For instance, in some embodiments, system 100 implements“target-side” deduplication by deduplicating data at the media agent 144after being received from data agent 142. In some such cases, mediaagents 144 are generally configured to manage the deduplication process.For instance, one or more of the media agents 144 maintain acorresponding deduplication database that stores deduplicationinformation (e.g., datablock signatures). Examples of such aconfiguration are provided in U.S. Pat. No. 9,020,900. Instead of or incombination with “target-side” deduplication, “source-side” (or“client-side”) deduplication can also be performed, e.g., to reduce theamount of data to be transmitted by data agent 142 to media agent 144.Storage manager 140 may communicate with other components within system100 via network protocols and cloud service provider APIs to facilitatecloud-based deduplication/single instancing, as exemplified in U.S. Pat.No. 8,954,446. Some other deduplication/single instancing techniques aredescribed in U.S. Pat. Pub. No. 2006/0224846 and in U.S. Pat. No.9,098,495.

Information Lifecycle Management and Hierarchical Storage Management

In some embodiments, files and other data over their lifetime move frommore expensive quick-access storage to less expensive slower-accessstorage. Operations associated with moving data through various tiers ofstorage are sometimes referred to as information lifecycle management(ILM) operations.

One type of ILM operation is a hierarchical storage management (HSM)operation, which generally automatically moves data between classes ofstorage devices, such as from high-cost to low-cost storage devices. Forinstance, an HSM operation may involve movement of data from primarystorage devices 104 to secondary storage devices 108, or between tiersof secondary storage devices 108. With each tier, the storage devicesmay be progressively cheaper, have relatively slower access/restoretimes, etc. For example, movement of data between tiers may occur asdata becomes less important over time. In some embodiments, an HSMoperation is similar to archiving in that creating an HSM copy may(though not always) involve deleting some of the source data, e.g.,according to one or more criteria related to the source data. Forexample, an HSM copy may include primary data 112 or a secondary copy116 that exceeds a given size threshold or a given age threshold. Often,and unlike some types of archive copies, HSM data that is removed oraged from the source is replaced by a logical reference pointer or stub.The reference pointer or stub can be stored in the primary storagedevice 104 or other source storage device, such as a secondary storagedevice 108 to replace the deleted source data and to point to orotherwise indicate the new location in (another) secondary storagedevice 108.

For example, files are generally moved between higher and lower coststorage depending on how often the files are accessed. When a userrequests access to HSM data that has been removed or migrated, system100 uses the stub to locate the data and may make recovery of the dataappear transparent, even though the HSM data may be stored at a locationdifferent from other source data. In this manner, the data appears tothe user (e.g., in file system browsing windows and the like) as if itstill resides in the source location (e.g., in a primary storage device104). The stub may include metadata associated with the correspondingdata, so that a file system and/or application can provide someinformation about the data object and/or a limited-functionality version(e.g., a preview) of the data object.

An HSM copy may be stored in a format other than the native applicationformat (e.g., compressed, encrypted, deduplicated, and/or otherwisemodified). In some cases, copies which involve the removal of data fromsource storage and the maintenance of stub or other logical referenceinformation on source storage may be referred to generally as “on-linearchive copies.” On the other hand, copies which involve the removal ofdata from source storage without the maintenance of stub or otherlogical reference information on source storage may be referred to as“off-line archive copies.” Examples of HSM and ILM techniques areprovided in U.S. Pat. No. 7,343,453.

Auxiliary Copy Operations

An auxiliary copy is generally a copy of an existing secondary copy 116.For instance, an initial secondary copy 116 may be derived from primarydata 112 or from data residing in secondary storage subsystem 118,whereas an auxiliary copy is generated from the initial secondary copy116. Auxiliary copies provide additional standby copies of data and mayreside on different secondary storage devices 108 than the initialsecondary copies 116. Thus, auxiliary copies can be used for recoverypurposes if initial secondary copies 116 become unavailable. Exemplaryauxiliary copy techniques are described in further detail in U.S. Pat.No. 8,230,195.

Disaster-Recovery Copy Operations

System 100 may also make and retain disaster recovery copies, often assecondary, high-availability disk copies. System 100 may createsecondary copies and store them at disaster recovery locations usingauxiliary copy or replication operations, such as continuous datareplication technologies. Depending on the particular data protectiongoals, disaster recovery locations can be remote from the clientcomputing devices 102 and primary storage devices 104, remote from someor all of the secondary storage devices 108, or both.

Data Manipulation, Including Encryption and Compression

Data manipulation and processing may include encryption and compressionas well as integrity marking and checking, formatting for transmission,formatting for storage, etc. Data may be manipulated “client-side” bydata agent 142 as well as “target-side” by media agent 144 in the courseof creating secondary copy 116, or conversely in the course of restoringdata from secondary to primary.

Encryption Operations

System 100 in some cases is configured to process data (e.g., files orother data objects, primary data 112, secondary copies 116, etc.),according to an appropriate encryption algorithm (e.g., Blowfish,Advanced Encryption Standard (AES), Triple Data Encryption Standard(3-DES), etc.) to limit access and provide data security. System 100 insome cases encrypts the data at the client level, such that clientcomputing devices 102 (e.g., data agents 142) encrypt the data prior totransferring it to other components, e.g., before sending the data tomedia agents 144 during a secondary copy operation. In such cases,client computing device 102 may maintain or have access to an encryptionkey or passphrase for decrypting the data upon restore. Encryption canalso occur when media agent 144 creates auxiliary copies or archivecopies. Encryption may be applied in creating a secondary copy 116 of apreviously unencrypted secondary copy 116, without limitation. Infurther embodiments, secondary storage devices 108 can implementbuilt-in, high performance hardware-based encryption.

Compression Operations

Similar to encryption, system 100 may also or alternatively compressdata in the course of generating a secondary copy 116. Compressionencodes information such that fewer bits are needed to represent theinformation as compared to the original representation. Compressiontechniques are well known in the art. Compression operations may applyone or more data compression algorithms. Compression may be applied increating a secondary copy 116 of a previously uncompressed secondarycopy, e.g., when making archive copies or disaster recovery copies. Theuse of compression may result in metadata that specifies the nature ofthe compression, so that data may be uncompressed on restore ifappropriate.

Data Analysis, Reporting, and Management Operations

Data analysis, reporting, and management operations can differ from datamovement operations in that they do not necessarily involve copying,migration or other transfer of data between different locations in thesystem. For instance, data analysis operations may involve processing(e.g., offline processing) or modification of already stored primarydata 112 and/or secondary copies 116. However, in some embodiments dataanalysis operations are performed in conjunction with data movementoperations. Some data analysis operations include content indexingoperations and classification operations which can be useful inleveraging data under management to enhance search and other features.

Classification Operations/Content Indexing

In some embodiments, information management system 100 analyzes andindexes characteristics, content, and metadata associated with primarydata 112 (“online content indexing”) and/or secondary copies 116(“off-line content indexing”). Content indexing can identify files orother data objects based on content (e.g., user-defined keywords orphrases, other keywords/phrases that are not defined by a user, etc.),and/or metadata (e.g., email metadata such as “to,” “from,” “cc,” “bcc,”attachment name, received time, etc.). Content indexes may be searchedand search results may be restored.

System 100 generally organizes and catalogues the results into a contentindex, which may be stored within media agent database 152, for example.The content index can also include the storage locations of or pointerreferences to indexed data in primary data 112 and/or secondary copies116. Results may also be stored elsewhere in system 100 (e.g., inprimary storage device 104 or in secondary storage device 108). Suchcontent index data provides storage manager 140 or other components withan efficient mechanism for locating primary data 112 and/or secondarycopies 116 of data objects that match particular criteria, thus greatlyincreasing the search speed capability of system 100. For instance,search criteria can be specified by a user through user interface 158 ofstorage manager 140. Moreover, when system 100 analyzes data and/ormetadata in secondary copies 116 to create an “off-line content index,”this operation has no significant impact on the performance of clientcomputing devices 102 and thus does not take a toll on the productionenvironment. Examples of content indexing techniques are provided inU.S. Pat. No. 8,170,995.

One or more components, such as a content index engine, can beconfigured to scan data and/or associated metadata for classificationpurposes to populate a database (or other data structure) ofinformation, which can be referred to as a “data classificationdatabase” or a “metabase.” Depending on the embodiment, the dataclassification database(s) can be organized in a variety of differentways, including centralization, logical sub-divisions, and/or physicalsub-divisions. For instance, one or more data classification databasesmay be associated with different subsystems or tiers within system 100.As an example, there may be a first metabase associated with primarystorage subsystem 117 and a second metabase associated with secondarystorage subsystem 118. In other cases, metabase(s) may be associatedwith individual components, e.g., client computing devices 102 and/ormedia agents 144. In some embodiments, a data classification databasemay reside as one or more data structures within management database146, may be otherwise associated with storage manager 140, and/or mayreside as a separate component. In some cases, metabase(s) may beincluded in separate database(s) and/or on separate storage device(s)from primary data 112 and/or secondary copies 116, such that operationsrelated to the metabase(s) do not significantly impact performance onother components of system 100. In other cases, metabase(s) may bestored along with primary data 112 and/or secondary copies 116. Files orother data objects can be associated with identifiers (e.g., tagentries, etc.) to facilitate searches of stored data objects. Among anumber of other benefits, the metabase can also allow efficient,automatic identification of files or other data objects to associatewith secondary copy or other information management operations. Forinstance, a metabase can dramatically improve the speed with whichsystem 100 can search through and identify data as compared to otherapproaches that involve scanning an entire file system. Examples ofmetabases and data classification operations are provided in U.S. Pat.Nos. 7,734,669 and 7,747,579.

Management and Reporting Operations

Certain embodiments leverage the integrated ubiquitous nature of system100 to provide useful system-wide management and reporting. Operationsmanagement can generally include monitoring and managing the health andperformance of system 100 by, without limitation, performing errortracking, generating granular storage/performance metrics (e.g., jobsuccess/failure information, deduplication efficiency, etc.), generatingstorage modeling and costing information, and the like. As an example,storage manager 140 or another component in system 100 may analyzetraffic patterns and suggest and/or automatically route data to minimizecongestion. In some embodiments, the system can generate predictionsrelating to storage operations or storage operation information. Suchpredictions, which may be based on a trending analysis, may predictvarious network operations or resource usage, such as network trafficlevels, storage media use, use of bandwidth of communication links, useof media agent components, etc. Further examples of traffic analysis,trend analysis, prediction generation, and the like are described inU.S. Pat. No. 7,343,453.

In some configurations having a hierarchy of storage operation cells, amaster storage manager 140 may track the status of subordinate cells,such as the status of jobs, system components, system resources, andother items, by communicating with storage managers 140 (or othercomponents) in the respective storage operation cells. Moreover, themaster storage manager 140 may also track status by receiving periodicstatus updates from the storage managers 140 (or other components) inthe respective cells regarding jobs, system components, systemresources, and other items. In some embodiments, a master storagemanager 140 may store status information and other information regardingits associated storage operation cells and other system information inits management database 146 and/or index 150 (or in another location).The master storage manager 140 or other component may also determinewhether certain storage-related or other criteria are satisfied, and mayperform an action or trigger event (e.g., data migration) in response tothe criteria being satisfied, such as where a storage threshold is metfor a particular volume, or where inadequate protection exists forcertain data. For instance, data from one or more storage operationcells is used to dynamically and automatically mitigate recognizedrisks, and/or to advise users of risks or suggest actions to mitigatethese risks. For example, an information management policy may specifycertain requirements (e.g., that a storage device should maintain acertain amount of free space, that secondary copies should occur at aparticular interval, that data should be aged and migrated to otherstorage after a particular period, that data on a secondary volumeshould always have a certain level of availability and be restorablewithin a given time period, that data on a secondary volume may bemirrored or otherwise migrated to a specified number of other volumes,etc.). If a risk condition or other criterion is triggered, the systemmay notify the user of these conditions and may suggest (orautomatically implement) a mitigation action to address the risk. Forexample, the system may indicate that data from a primary copy 112should be migrated to a secondary storage device 108 to free up space onprimary storage device 104. Examples of the use of risk factors andother triggering criteria are described in U.S. Pat. No. 7,343,453.

In some embodiments, system 100 may also determine whether a metric orother indication satisfies particular storage criteria sufficient toperform an action. For example, a storage policy or other definitionmight indicate that a storage manager 140 should initiate a particularaction if a storage metric or other indication drops below or otherwisefails to satisfy specified criteria such as a threshold of dataprotection. In some embodiments, risk factors may be quantified intocertain measurable service or risk levels. For example, certainapplications and associated data may be considered to be more importantrelative to other data and services. Financial compliance data, forexample, may be of greater importance than marketing materials, etc.Network administrators may assign priority values or “weights” tocertain data and/or applications corresponding to the relativeimportance. The level of compliance of secondary copy operationsspecified for these applications may also be assigned a certain value.Thus, the health, impact, and overall importance of a service may bedetermined, such as by measuring the compliance value and calculatingthe product of the priority value and the compliance value to determinethe “service level” and comparing it to certain operational thresholdsto determine whether it is acceptable. Further examples of the servicelevel determination are provided in U.S. Pat. No. 7,343,453.

System 100 may additionally calculate data costing and data availabilityassociated with information management operation cells. For instance,data received from a cell may be used in conjunction withhardware-related information and other information about system elementsto determine the cost of storage and/or the availability of particulardata. Exemplary information generated could include how fast aparticular department is using up available storage space, how long datawould take to recover over a particular pathway from a particularsecondary storage device, costs over time, etc. Moreover, in someembodiments, such information may be used to determine or predict theoverall cost associated with the storage of certain information. Thecost associated with hosting a certain application may be based, atleast in part, on the type of media on which the data resides, forexample. Storage devices may be assigned to a particular costcategories, for example. Further examples of costing techniques aredescribed in U.S. Pat. No. 7,343,453.

Any of the above types of information (e.g., information related totrending, predictions, job, cell or component status, risk, servicelevel, costing, etc.) can generally be provided to users via userinterface 158 in a single integrated view or console (not shown). Reporttypes may include: scheduling, event management, media management anddata aging. Available reports may also include backup history, dataaging history, auxiliary copy history, job history, library and drive,media in library, restore history, and storage policy, etc., withoutlimitation. Such reports may be specified and created at a certain pointin time as a system analysis, forecasting, or provisioning tool.Integrated reports may also be generated that illustrate storage andperformance metrics, risks and storage costing information. Moreover,users may create their own reports based on specific needs. Userinterface 158 can include an option to graphically depict the variouscomponents in the system using appropriate icons. As one example, userinterface 158 may provide a graphical depiction of primary storagedevices 104, secondary storage devices 108, data agents 142 and/or mediaagents 144, and their relationship to one another in system 100.

In general, the operations management functionality of system 100 canfacilitate planning and decision-making. For example, in someembodiments, a user may view the status of some or all jobs as well asthe status of each component of information management system 100. Usersmay then plan and make decisions based on this data. For instance, auser may view high-level information regarding secondary copy operationsfor system 100, such as job status, component status, resource status(e.g., communication pathways, etc.), and other information. The usermay also drill down or use other means to obtain more detailedinformation regarding a particular component, job, or the like. Furtherexamples are provided in U.S. Pat. No. 7,343,453.

System 100 can also be configured to perform system-wide e-discoveryoperations in some embodiments. In general, e-discovery operationsprovide a unified collection and search capability for data in thesystem, such as data stored in secondary storage devices 108 (e.g.,backups, archives, or other secondary copies 116). For example, system100 may construct and maintain a virtual repository for data stored insystem 100 that is integrated across source applications 110, differentstorage device types, etc. According to some embodiments, e-discoveryutilizes other techniques described herein, such as data classificationand/or content indexing.

Information Management Policies

An information management policy 148 can include a data structure orother information source that specifies a set of parameters (e.g.,criteria and rules) associated with secondary copy and/or otherinformation management operations.

One type of information management policy 148 is a “storage policy.”According to certain embodiments, a storage policy generally comprises adata structure or other information source that defines (or includesinformation sufficient to determine) a set of preferences or othercriteria for performing information management operations. Storagepolicies can include one or more of the following: (1) what data will beassociated with the storage policy, e.g., subclient; (2) a destinationto which the data will be stored; (3) datapath information specifyinghow the data will be communicated to the destination; (4) the type ofsecondary copy operation to be performed; and (5) retention informationspecifying how long the data will be retained at the destination (see,e.g., FIG. 1E). Data associated with a storage policy can be logicallyorganized into subclients, which may represent primary data 112 and/orsecondary copies 116. A subclient may represent static or dynamicassociations of portions of a data volume. Subclients may representmutually exclusive portions. Thus, in certain embodiments, a portion ofdata may be given a label and the association is stored as a staticentity in an index, database or other storage location. Subclients mayalso be used as an effective administrative scheme of organizing dataaccording to data type, department within the enterprise, storagepreferences, or the like. Depending on the configuration, subclients cancorrespond to files, folders, virtual machines, databases, etc. In oneexemplary scenario, an administrator may find it preferable to separatee-mail data from financial data using two different subclients.

A storage policy can define where data is stored by specifying a targetor destination storage device (or group of storage devices). Forinstance, where the secondary storage device 108 includes a group ofdisk libraries, the storage policy may specify a particular disk libraryfor storing the subclients associated with the policy. As anotherexample, where the secondary storage devices 108 include one or moretape libraries, the storage policy may specify a particular tape libraryfor storing the subclients associated with the storage policy, and mayalso specify a drive pool and a tape pool defining a group of tapedrives and a group of tapes, respectively, for use in storing thesubclient data. While information in the storage policy can bestatically assigned in some cases, some or all of the information in thestorage policy can also be dynamically determined based on criteria setforth in the storage policy. For instance, based on such criteria, aparticular destination storage device(s) or other parameter of thestorage policy may be determined based on characteristics associatedwith the data involved in a particular secondary copy operation, deviceavailability (e.g., availability of a secondary storage device 108 or amedia agent 144), network status and conditions (e.g., identifiedbottlenecks), user credentials, and the like.

Datapath information can also be included in the storage policy. Forinstance, the storage policy may specify network pathways and componentsto utilize when moving the data to the destination storage device(s). Insome embodiments, the storage policy specifies one or more media agents144 for conveying data associated with the storage policy between thesource and destination. A storage policy can also specify the type(s) ofassociated operations, such as backup, archive, snapshot, auxiliarycopy, or the like. Furthermore, retention parameters can specify howlong the resulting secondary copies 116 will be kept (e.g., a number ofdays, months, years, etc.), perhaps depending on organizational needsand/or compliance criteria.

When adding a new client computing device 102, administrators canmanually configure information management policies 148 and/or othersettings, e.g., via user interface 158. However, this can be an involvedprocess resulting in delays, and it may be desirable to begin dataprotection operations quickly, without awaiting human intervention.Thus, in some embodiments, system 100 automatically applies a defaultconfiguration to client computing device 102. As one example, when oneor more data agent(s) 142 are installed on a client computing device102, the installation script may register the client computing device102 with storage manager 140, which in turn applies the defaultconfiguration to the new client computing device 102. In this manner,data protection operations can begin substantially immediately. Thedefault configuration can include a default storage policy, for example,and can specify any appropriate information sufficient to begin dataprotection operations. This can include a type of data protectionoperation, scheduling information, a target secondary storage device108, data path information (e.g., a particular media agent 144), and thelike.

Another type of information management policy 148 is a “schedulingpolicy,” which specifies when and how often to perform operations.Scheduling parameters may specify with what frequency (e.g., hourly,weekly, daily, event-based, etc.) or under what triggering conditionssecondary copy or other information management operations are to takeplace. Scheduling policies in some cases are associated with particularcomponents, such as a subclient, client computing device 102, and thelike.

Another type of information management policy 148 is an “audit policy”(or “security policy”), which comprises preferences, rules and/orcriteria that protect sensitive data in system 100. For example, anaudit policy may define “sensitive objects” which are files or dataobjects that contain particular keywords (e.g., “confidential,” or“privileged”) and/or are associated with particular keywords (e.g., inmetadata) or particular flags (e.g., in metadata identifying a documentor email as personal, confidential, etc.). An audit policy may furtherspecify rules for handling sensitive objects. As an example, an auditpolicy may require that a reviewer approve the transfer of any sensitiveobjects to a cloud storage site, and that if approval is denied for aparticular sensitive object, the sensitive object should be transferredto a local primary storage device 104 instead. To facilitate thisapproval, the audit policy may further specify how a secondary storagecomputing device 106 or other system component should notify a reviewerthat a sensitive object is slated for transfer.

Another type of information management policy 148 is a “provisioningpolicy,” which can include preferences, priorities, rules, and/orcriteria that specify how client computing devices 102 (or groupsthereof) may utilize system resources, such as available storage oncloud storage and/or network bandwidth. A provisioning policy specifies,for example, data quotas for particular client computing devices 102(e.g., a number of gigabytes that can be stored monthly, quarterly orannually). Storage manager 140 or other components may enforce theprovisioning policy. For instance, media agents 144 may enforce thepolicy when transferring data to secondary storage devices 108. If aclient computing device 102 exceeds a quota, a budget for the clientcomputing device 102 (or associated department) may be adjustedaccordingly or an alert may trigger.

While the above types of information management policies 148 aredescribed as separate policies, one or more of these can be generallycombined into a single information management policy 148. For instance,a storage policy may also include or otherwise be associated with one ormore scheduling, audit, or provisioning policies or operationalparameters thereof. Moreover, while storage policies are typicallyassociated with moving and storing data, other policies may beassociated with other types of information management operations. Thefollowing is a non-exhaustive list of items that information managementpolicies 148 may specify:

-   -   schedules or other timing information, e.g., specifying when        and/or how often to perform information management operations;    -   the type of secondary copy 116 and/or copy format (e.g.,        snapshot, backup, archive, HSM, etc.);    -   a location or a class or quality of storage for storing        secondary copies 116 (e.g., one or more particular secondary        storage devices 108);    -   preferences regarding whether and how to encrypt, compress,        deduplicate, or otherwise modify or transform secondary copies        116;    -   which system components and/or network pathways (e.g., preferred        media agents 144) should be used to perform secondary storage        operations;    -   resource allocation among different computing devices or other        system components used in performing information management        operations (e.g., bandwidth allocation, available storage        capacity, etc.);    -   whether and how to synchronize or otherwise distribute files or        other data objects across multiple computing devices or hosted        services; and    -   retention information specifying the length of time primary data        112 and/or secondary copies 116 should be retained, e.g., in a        particular class or tier of storage devices, or within the        system 100.

Information management policies 148 can additionally specify or dependon historical or current criteria that may be used to determine whichrules to apply to a particular data object, system component, orinformation management operation, such as:

-   -   frequency with which primary data 112 or a secondary copy 116 of        a data object or metadata has been or is predicted to be used,        accessed, or modified;    -   time-related factors (e.g., aging information such as time since        the creation or modification of a data object);    -   deduplication information (e.g., hashes, data blocks,        deduplication block size, deduplication efficiency or other        metrics);    -   an estimated or historic usage or cost associated with different        components (e.g., with secondary storage devices 108);    -   the identity of users, applications 110, client computing        devices 102 and/or other computing devices that created,        accessed, modified, or otherwise utilized primary data 112 or        secondary copies 116;    -   a relative sensitivity (e.g., confidentiality, importance) of a        data object, e.g., as determined by its content and/or metadata;    -   the current or historical storage capacity of various storage        devices;    -   the current or historical network capacity of network pathways        connecting various components within the storage operation cell;    -   access control lists or other security information; and    -   the content of a particular data object (e.g., its textual        content) or of metadata associated with the data object.

Exemplary Storage Policy and Secondary Copy Operations

FIG. 1E includes a data flow diagram depicting performance of secondarycopy operations by an embodiment of information management system 100,according to an exemplary storage policy 148A. System 100 includes astorage manager 140, a client computing device 102 having a file systemdata agent 142A and an email data agent 142B operating thereon, aprimary storage device 104, two media agents 144A, 144B, and twosecondary storage devices 108: a disk library 108A and a tape library108B. As shown, primary storage device 104 includes primary data 112A,which is associated with a logical grouping of data associated with afile system (“file system subclient”), and primary data 112B, which is alogical grouping of data associated with email (“email subclient”). Thetechniques described with respect to FIG. 1E can be utilized inconjunction with data that is otherwise organized as well.

As indicated by the dashed box, the second media agent 144B and tapelibrary 1088 are “off-site,” and may be remotely located from the othercomponents in system 100 (e.g., in a different city, office building,etc.). Indeed, “off-site” may refer to a magnetic tape located in remotestorage, which must be manually retrieved and loaded into a tape driveto be read. In this manner, information stored on the tape library 108Bmay provide protection in the event of a disaster or other failure atthe main site(s) where data is stored.

The file system subclient 112A in certain embodiments generallycomprises information generated by the file system and/or operatingsystem of client computing device 102, and can include, for example,file system data (e.g., regular files, file tables, mount points, etc.),operating system data (e.g., registries, event logs, etc.), and thelike. The e-mail subclient 1128 can include data generated by an e-mailapplication operating on client computing device 102, e.g., mailboxinformation, folder information, emails, attachments, associateddatabase information, and the like. As described above, the subclientscan be logical containers, and the data included in the correspondingprimary data 112A and 112B may or may not be stored contiguously.

The exemplary storage policy 148A includes backup copy preferences orrule set 160, disaster recovery copy preferences or rule set 162, andcompliance copy preferences or rule set 164. Backup copy rule set 160specifies that it is associated with file system subclient 166 and emailsubclient 168. Each of subclients 166 and 168 are associated with theparticular client computing device 102. Backup copy rule set 160 furtherspecifies that the backup operation will be written to disk library 108Aand designates a particular media agent 144A to convey the data to disklibrary 108A. Finally, backup copy rule set 160 specifies that backupcopies created according to rule set 160 are scheduled to be generatedhourly and are to be retained for 30 days. In some other embodiments,scheduling information is not included in storage policy 148A and isinstead specified by a separate scheduling policy.

Disaster recovery copy rule set 162 is associated with the same twosubclients 166 and 168. However, disaster recovery copy rule set 162 isassociated with tape library 108B, unlike backup copy rule set 160.Moreover, disaster recovery copy rule set 162 specifies that a differentmedia agent, namely 144B, will convey data to tape library 108B.Disaster recovery copies created according to rule set 162 will beretained for 60 days and will be generated daily. Disaster recoverycopies generated according to disaster recovery copy rule set 162 canprovide protection in the event of a disaster or other catastrophic dataloss that would affect the backup copy 116A maintained on disk library108A.

Compliance copy rule set 164 is only associated with the email subclient168, and not the file system subclient 166. Compliance copies generatedaccording to compliance copy rule set 164 will therefore not includeprimary data 112A from the file system subclient 166. For instance, theorganization may be under an obligation to store and maintain copies ofemail data for a particular period of time (e.g., 10 years) to complywith state or federal regulations, while similar regulations do notapply to file system data. Compliance copy rule set 164 is associatedwith the same tape library 108B and media agent 144B as disasterrecovery copy rule set 162, although a different storage device or mediaagent could be used in other embodiments. Finally, compliance copy ruleset 164 specifies that the copies it governs will be generated quarterlyand retained for 10 years.

Secondary Copy Jobs

A logical grouping of secondary copy operations governed by a rule setand being initiated at a point in time may be referred to as a“secondary copy job” (and sometimes may be called a “backup job,” eventhough it is not necessarily limited to creating only backup copies).Secondary copy jobs may be initiated on demand as well. Steps 1-9 belowillustrate three secondary copy jobs based on storage policy 148A.

Referring to FIG. 1E, at step 1, storage manager 140 initiates a backupjob according to the backup copy rule set 160, which logically comprisesall the secondary copy operations necessary to effectuate rules 160 instorage policy 148A every hour, including steps 1-4 occurring hourly.For instance, a scheduling service running on storage manager 140accesses backup copy rule set 160 or a separate scheduling policyassociated with client computing device 102 and initiates a backup jobon an hourly basis. Thus, at the scheduled time, storage manager 140sends instructions to client computing device 102 (i.e., to both dataagent 142A and data agent 142B) to begin the backup job.

At step 2, file system data agent 142A and email data agent 142B onclient computing device 102 respond to instructions from storage manager140 by accessing and processing the respective subclient primary data112A and 112B involved in the backup copy operation, which can be foundin primary storage device 104. Because the secondary copy operation is abackup copy operation, the data agent(s) 142A, 142B may format the datainto a backup format or otherwise process the data suitable for a backupcopy.

At step 3, client computing device 102 communicates the processed filesystem data (e.g., using file system data agent 142A) and the processedemail data (e.g., using email data agent 142B) to the first media agent144A according to backup copy rule set 160, as directed by storagemanager 140. Storage manager 140 may further keep a record in managementdatabase 146 of the association between media agent 144A and one or moreof: client computing device 102, file system subclient 112A, file systemdata agent 142A, email subclient 112B, email data agent 142B, and/orbackup copy 116A.

The target media agent 144A receives the data-agent-processed data fromclient computing device 102, and at step 4 generates and conveys backupcopy 116A to disk library 108A to be stored as backup copy 116A, againat the direction of storage manager 140 and according to backup copyrule set 160. Media agent 144A can also update its index 153 to includedata and/or metadata related to backup copy 116A, such as informationindicating where the backup copy 116A resides on disk library 108A,where the email copy resides, where the file system copy resides, dataand metadata for cache retrieval, etc. Storage manager 140 may similarlyupdate its index 150 to include information relating to the secondarycopy operation, such as information relating to the type of operation, aphysical location associated with one or more copies created by theoperation, the time the operation was performed, status informationrelating to the operation, the components involved in the operation, andthe like. In some cases, storage manager 140 may update its index 150 toinclude some or all of the information stored in index 153 of mediaagent 144A. At this point, the backup job may be considered complete.After the 30-day retention period expires, storage manager 140 instructsmedia agent 144A to delete backup copy 116A from disk library 108A andindexes 150 and/or 153 are updated accordingly.

At step 5, storage manager 140 initiates another backup job for adisaster recovery copy according to the disaster recovery rule set 162.Illustratively this includes steps 5-7 occurring daily for creatingdisaster recovery copy 116B. Illustratively, and by way of illustratingthe scalable aspects and off-loading principles embedded in system 100,disaster recovery copy 116B is based on backup copy 116A and not onprimary data 112A and 112B.

At step 6, illustratively based on instructions received from storagemanager 140 at step 5, the specified media agent 144B retrieves the mostrecent backup copy 116A from disk library 108A.

At step 7, again at the direction of storage manager 140 and asspecified in disaster recovery copy rule set 162, media agent 144B usesthe retrieved data to create a disaster recovery copy 116B and store itto tape library 108B. In some cases, disaster recovery copy 116B is adirect, mirror copy of backup copy 116A, and remains in the backupformat. In other embodiments, disaster recovery copy 116B may be furthercompressed or encrypted, or may be generated in some other manner, suchas by using primary data 112A and 112B from primary storage device 104as sources. The disaster recovery copy operation is initiated once a dayand disaster recovery copies 116B are deleted after 60 days; indexes 153and/or 150 are updated accordingly when/after each informationmanagement operation is executed and/or completed. The present backupjob may be considered completed.

At step 8, storage manager 140 initiates another backup job according tocompliance rule set 164, which performs steps 8-9 quarterly to createcompliance copy 116C. For instance, storage manager 140 instructs mediaagent 144B to create compliance copy 116C on tape library 108B, asspecified in the compliance copy rule set 164.

At step 9 in the example, compliance copy 116C is generated usingdisaster recovery copy 116B as the source. This is efficient, becausedisaster recovery copy resides on the same secondary storage device andthus no network resources are required to move the data. In otherembodiments, compliance copy 116C is instead generated using primarydata 112B corresponding to the email subclient or using backup copy 116Afrom disk library 108A as source data. As specified in the illustratedexample, compliance copies 116C are created quarterly, and are deletedafter ten years, and indexes 153 and/or 150 are kept up-to-dateaccordingly.

Exemplary Applications of Storage Policies—Information GovernancePolicies and Classification

Again referring to FIG. 1E, storage manager 140 may permit a user tospecify aspects of storage policy 148A. For example, the storage policycan be modified to include information governance policies to define howdata should be managed in order to comply with a certain regulation orbusiness objective. The various policies may be stored, for example, inmanagement database 146. An information governance policy may align withone or more compliance tasks that are imposed by regulations or businessrequirements. Examples of information governance policies might includea Sarbanes-Oxley policy, a HIPAA policy, an electronic discovery(e-discovery) policy, and so on.

Information governance policies allow administrators to obtain differentperspectives on an organization's online and offline data, without theneed for a dedicated data silo created solely for each differentviewpoint. As described previously, the data storage systems hereinbuild an index that reflects the contents of a distributed data set thatspans numerous clients and storage devices, including both primary dataand secondary copies, and online and offline copies. An organization mayapply multiple information governance policies in a top-down manner overthat unified data set and indexing schema in order to view andmanipulate the data set through different lenses, each of which isadapted to a particular compliance or business goal. Thus, for example,by applying an e-discovery policy and a Sarbanes-Oxley policy, twodifferent groups of users in an organization can conduct two verydifferent analyses of the same underlying physical set of data/copies,which may be distributed throughout the information management system.

An information governance policy may comprise a classification policy,which defines a taxonomy of classification terms or tags relevant to acompliance task and/or business objective. A classification policy mayalso associate a defined tag with a classification rule. Aclassification rule defines a particular combination of criteria, suchas users who have created, accessed or modified a document or dataobject; file or application types; content or metadata keywords; clientsor storage locations; dates of data creation and/or access; reviewstatus or other status within a workflow (e.g., reviewed orun-reviewed); modification times or types of modifications; and/or anyother data attributes in any combination, without limitation. Aclassification rule may also be defined using other classification tagsin the taxonomy. The various criteria used to define a classificationrule may be combined in any suitable fashion, for example, via Booleanoperators, to define a complex classification rule. As an example, ane-discovery classification policy might define a classification tag“privileged” that is associated with documents or data objects that (1)were created or modified by legal department staff, or (2) were sent toor received from outside counsel via email, or (3) contain one of thefollowing keywords: “privileged” or “attorney” or “counsel,” or otherlike terms. Accordingly, all these documents or data objects will beclassified as “privileged.”

One specific type of classification tag, which may be added to an indexat the time of indexing, is an “entity tag.” An entity tag may be, forexample, any content that matches a defined data mask format. Examplesof entity tags might include, e.g., social security numbers (e.g., anynumerical content matching the formatting mask XXX-XX-XXXX), credit cardnumbers (e.g., content having a 13-16 digit string of numbers), SKUnumbers, product numbers, etc. A user may define a classification policyby indicating criteria, parameters or descriptors of the policy via agraphical user interface, such as a form or page with fields to befilled in, pull-down menus or entries allowing one or more of severaloptions to be selected, buttons, sliders, hypertext links or other knownuser interface tools for receiving user input, etc. For example, a usermay define certain entity tags, such as a particular product number orproject ID. In some implementations, the classification policy can beimplemented using cloud-based techniques. For example, the storagedevices may be cloud storage devices, and the storage manager 140 mayexecute cloud service provider API over a network to classify datastored on cloud storage devices.

Restore Operations from Secondary Copies

While not shown in FIG. 1E, at some later point in time, a restoreoperation can be initiated involving one or more of secondary copies116A, 116B, and 116C. A restore operation logically takes a selectedsecondary copy 116, reverses the effects of the secondary copy operationthat created it, and stores the restored data to primary storage where aclient computing device 102 may properly access it as primary data. Amedia agent 144 and an appropriate data agent 142 (e.g., executing onthe client computing device 102) perform the tasks needed to complete arestore operation. For example, data that was encrypted, compressed,and/or deduplicated in the creation of secondary copy 116 will becorrespondingly rehydrated (reversing deduplication), uncompressed, andunencrypted into a format appropriate to primary data. Metadata storedwithin or associated with the secondary copy 116 may be used during therestore operation. In general, restored data should be indistinguishablefrom other primary data 112. Preferably, the restored data has fullyregained the native format that may make it immediately usable byapplication 110.

As one example, a user may manually initiate a restore of backup copy116A, e.g., by interacting with user interface 158 of storage manager140 or with a web-based console with access to system 100. Storagemanager 140 may accesses data in its index 150 and/or managementdatabase 146 (and/or the respective storage policy 148A) associated withthe selected backup copy 116A to identify the appropriate media agent144A and/or secondary storage device 108A where the secondary copyresides. The user may be presented with a representation (e.g., stub,thumbnail, listing, etc.) and metadata about the selected secondarycopy, in order to determine whether this is the appropriate copy to berestored, e.g., date that the original primary data was created. Storagemanager 140 will then instruct media agent 144A and an appropriate dataagent 142 on the target client computing device 102 to restore secondarycopy 116A to primary storage device 104. A media agent may be selectedfor use in the restore operation based on a load balancing algorithm, anavailability based algorithm, or other criteria. The selected mediaagent, e.g., 144A, retrieves secondary copy 116A from disk library 108A.For instance, media agent 144A may access its index 153 to identify alocation of backup copy 116A on disk library 108A, or may accesslocation information residing on disk library 108A itself.

In some cases a backup copy 116A that was recently created or accessed,may be cached to speed up the restore operation. In such a case, mediaagent 144A accesses a cached version of backup copy 116A residing inindex 153, without having to access disk library 108A for some or all ofthe data. Once it has retrieved backup copy 116A, the media agent 144Acommunicates the data to the requesting client computing device 102.Upon receipt, file system data agent 142A and email data agent 142B mayunpack (e.g., restore from a backup format to the native applicationformat) the data in backup copy 116A and restore the unpackaged data toprimary storage device 104. In general, secondary copies 116 may berestored to the same volume or folder in primary storage device 104 fromwhich the secondary copy was derived; to another storage location orclient computing device 102; to shared storage, etc. In some cases, thedata may be restored so that it may be used by an application 110 of adifferent version/vintage from the application that created the originalprimary data 112.

Exemplary Secondary Copy Formatting

The formatting and structure of secondary copies 116 can vary dependingon the embodiment. In some cases, secondary copies 116 are formatted asa series of logical data units or “chunks” (e.g., 512 MB, 1 GB, 2 GB, 4GB, or 8 GB chunks). This can facilitate efficient communication andwriting to secondary storage devices 108, e.g., according to resourceavailability. For example, a single secondary copy 116 may be written ona chunk-by-chunk basis to one or more secondary storage devices 108. Insome cases, users can select different chunk sizes, e.g., to improvethroughput to tape storage devices. Generally, each chunk can include aheader and a payload. The payload can include files (or other dataunits) or subsets thereof included in the chunk, whereas the chunkheader generally includes metadata relating to the chunk, some or all ofwhich may be derived from the payload. For example, during a secondarycopy operation, media agent 144, storage manager 140, or other componentmay divide files into chunks and generate headers for each chunk byprocessing the files. Headers can include a variety of information suchas file and/or volume identifier(s), offset(s), and/or other informationassociated with the payload data items, a chunk sequence number, etc.Importantly, in addition to being stored with secondary copy 116 onsecondary storage device 108, chunk headers can also be stored to index153 of the associated media agent(s) 144 and/or to index 150 associatedwith storage manager 140. This can be useful for providing fasterprocessing of secondary copies 116 during browsing, restores, or otheroperations. In some cases, once a chunk is successfully transferred to asecondary storage device 108, the secondary storage device 108 returnsan indication of receipt, e.g., to media agent 144 and/or storagemanager 140, which may update their respective indexes 153, 150accordingly. During restore, chunks may be processed (e.g., by mediaagent 144) according to the information in the chunk header toreassemble the files.

Data can also be communicated within system 100 in data channels thatconnect client computing devices 102 to secondary storage devices 108.These data channels can be referred to as “data streams,” and multipledata streams can be employed to parallelize an information managementoperation, improving data transfer rate, among other advantages. Exampledata formatting techniques including techniques involving datastreaming, chunking, and the use of other data structures in creatingsecondary copies are described in U.S. Pat. Nos. 7,315,923, 8,156,086,and 8,578,120.

FIGS. 1F and 1G are diagrams of example data streams 170 and 171,respectively, which may be employed for performing informationmanagement operations. Referring to FIG. 1F, data agent 142 forms datastream 170 from source data associated with a client computing device102 (e.g., primary data 112). Data stream 170 is composed of multiplepairs of stream header 172 and stream data (or stream payload) 174. Datastreams 170 and 171 shown in the illustrated example are for asingle-instanced storage operation, and a stream payload 174 thereforemay include both single-instance (SI) data and/or non-SI data. A streamheader 172 includes metadata about the stream payload 174. This metadatamay include, for example, a length of the stream payload 174, anindication of whether the stream payload 174 is encrypted, an indicationof whether the stream payload 174 is compressed, an archive fileidentifier (ID), an indication of whether the stream payload 174 issingle instanceable, and an indication of whether the stream payload 174is a start of a block of data.

Referring to FIG. 1G, data stream 171 has the stream header 172 andstream payload 174 aligned into multiple data blocks. In this example,the data blocks are of size 64 KB. The first two stream header 172 andstream payload 174 pairs comprise a first data block of size 64 KB. Thefirst stream header 172 indicates that the length of the succeedingstream payload 174 is 63 KB and that it is the start of a data block.The next stream header 172 indicates that the succeeding stream payload174 has a length of 1 KB and that it is not the start of a new datablock. Immediately following stream payload 174 is a pair comprising anidentifier header 176 and identifier data 178. The identifier header 176includes an indication that the succeeding identifier data 178 includesthe identifier for the immediately previous data block. The identifierdata 178 includes the identifier that the data agent 142 generated forthe data block. The data stream 171 also includes other stream header172 and stream payload 174 pairs, which may be for SI data and/or non-SIdata.

FIG. 1H is a diagram illustrating data structures 180 that may be usedto store blocks of SI data and non-SI data on a storage device (e.g.,secondary storage device 108). According to certain embodiments, datastructures 180 do not form part of a native file system of the storagedevice. Data structures 180 include one or more volume folders 182, oneor more chunk folders 184/185 within the volume folder 182, and multiplefiles within chunk folder 184. Each chunk folder 184/185 includes ametadata file 186/187, a metadata index file 188/189, one or morecontainer files 190/191/193, and a container index file 192/194.Metadata file 186/187 stores non-SI data blocks as well as links to SIdata blocks stored in container files. Metadata index file 188/189stores an index to the data in the metadata file 186/187. Containerfiles 190/191/193 store SI data blocks. Container index file 192/194stores an index to container files 190/191/193. Among other things,container index file 192/194 stores an indication of whether acorresponding block in a container file 190/191/193 is referred to by alink in a metadata file 186/187. For example, data block B2 in thecontainer file 190 is referred to by a link in metadata file 187 inchunk folder 185. Accordingly, the corresponding index entry incontainer index file 192 indicates that data block B2 in container file190 is referred to. As another example, data block B1 in container file191 is referred to by a link in metadata file 187, and so thecorresponding index entry in container index file 192 indicates thatthis data block is referred to.

As an example, data structures 180 illustrated in FIG. 1H may have beencreated as a result of separate secondary copy operations involving twoclient computing devices 102. For example, a first secondary copyoperation on a first client computing device 102 could result in thecreation of the first chunk folder 184, and a second secondary copyoperation on a second client computing device 102 could result in thecreation of the second chunk folder 185. Container files 190/191 in thefirst chunk folder 184 would contain the blocks of SI data of the firstclient computing device 102. If the two client computing devices 102have substantially similar data, the second secondary copy operation onthe data of the second client computing device 102 would result in mediaagent 144 storing primarily links to the data blocks of the first clientcomputing device 102 that are already stored in the container files190/191. Accordingly, while a first secondary copy operation may resultin storing nearly all of the data subject to the operation, subsequentsecondary storage operations involving similar data may result insubstantial data storage space savings, because links to already storeddata blocks can be stored instead of additional instances of datablocks.

If the operating system of the secondary storage computing device 106 onwhich media agent 144 operates supports sparse files, then when mediaagent 144 creates container files 190/191/193, it can create them assparse files. A sparse file is a type of file that may include emptyspace (e.g., a sparse file may have real data within it, such as at thebeginning of the file and/or at the end of the file, but may also haveempty space in it that is not storing actual data, such as a contiguousrange of bytes all having a value of zero). Having container files190/191/193 be sparse files allows media agent 144 to free up space incontainer files 190/191/193 when blocks of data in container files190/191/193 no longer need to be stored on the storage devices. In someexamples, media agent 144 creates a new container file 190/191/193 whena container file 190/191/193 either includes 100 blocks of data or whenthe size of the container file 190 exceeds 50 MB. In other examples,media agent 144 creates a new container file 190/191/193 when acontainer file 190/191/193 satisfies other criteria (e.g., it containsfrom approx. 100 to approx. 1000 blocks or when its size exceedsapproximately 50 MB to 1 GB). In some cases, a file on which a secondarycopy operation is performed may comprise a large number of data blocks.For example, a 100 MB file may comprise 400 data blocks of size 256 KB.If such a file is to be stored, its data blocks may span more than onecontainer file, or even more than one chunk folder. As another example,a database file of 20 GB may comprise over 40,000 data blocks of size512 KB. If such a database file is to be stored, its data blocks willlikely span multiple container files, multiple chunk folders, andpotentially multiple volume folders. Restoring such files may requireaccessing multiple container files, chunk folders, and/or volume foldersto obtain the requisite data blocks.

Using Backup Data for Replication and Disaster Recovery (“LiveSynchronization”)

There is an increased demand to off-load resource intensive informationmanagement tasks (e.g., data replication tasks) away from productiondevices (e.g., physical or virtual client computing devices) in order tomaximize production efficiency. At the same time, enterprises expectaccess to readily-available up-to-date recovery copies in the event offailure, with little or no production downtime.

FIG. 2A illustrates a system 200 configured to address these and otherissues by using backup or other secondary copy data to synchronize asource subsystem 201 (e.g., a production site) with a destinationsubsystem 203 (e.g., a failover site). Such a technique can be referredto as “live synchronization” and/or “live synchronization replication.”In the illustrated embodiment, the source client computing devices 202 ainclude one or more virtual machines (or “VMs”) executing on one or morecorresponding VM host computers 205 a, though the source need not bevirtualized. The destination site 203 may be at a location that isremote from the production site 201, or may be located in the same datacenter, without limitation. One or more of the production site 201 anddestination site 203 may reside at data centers at known geographiclocations, or alternatively may operate “in the cloud.”

The synchronization can be achieved by generally applying an ongoingstream of incremental backups from the source subsystem 201 to thedestination subsystem 203, such as according to what can be referred toas an “incremental forever” approach. FIG. 2A illustrates an embodimentof a data flow which may be orchestrated at the direction of one or morestorage managers (not shown). At step 1, the source data agent(s) 242 aand source media agent(s) 244 a work together to write backup or othersecondary copies of the primary data generated by the source clientcomputing devices 202 a into the source secondary storage device(s) 208a. At step 2, the backup/secondary copies are retrieved by the sourcemedia agent(s) 244 a from secondary storage. At step 3, source mediaagent(s) 244 a communicate the backup/secondary copies across a networkto the destination media agent(s) 244 b in destination subsystem 203.

As shown, the data can be copied from source to destination in anincremental fashion, such that only changed blocks are transmitted, andin some cases multiple incremental backups are consolidated at thesource so that only the most current changed blocks are transmitted toand applied at the destination. An example of live synchronization ofvirtual machines using the “incremental forever” approach is found inU.S. Patent Application No. 62/265,339 entitled “Live Synchronizationand Management of Virtual Machines across Computing and VirtualizationPlatforms and Using Live Synchronization to Support Disaster Recovery.”Moreover, a deduplicated copy can be employed to further reduce networktraffic from source to destination. For instance, the system can utilizethe deduplicated copy techniques described in U.S. Pat. No. 9,239,687,entitled “Systems and Methods for Retaining and Using Data BlockSignatures in Data Protection Operations.”

At step 4, destination media agent(s) 244 b write the receivedbackup/secondary copy data to the destination secondary storagedevice(s) 208 b. At step 5, the synchronization is completed when thedestination media agent(s) and destination data agent(s) 242 b restorethe backup/secondary copy data to the destination client computingdevice(s) 202 b. The destination client computing device(s) 202 b may bekept “warm” awaiting activation in case failure is detected at thesource. This synchronization/replication process can incorporate thetechniques described in U.S. patent application Ser. No. 14/721,971,entitled “Replication Using Deduplicated Secondary Copy Data.”

Where the incremental backups are applied on a frequent, on-going basis,the synchronized copies can be viewed as mirror or replication copies.Moreover, by applying the incremental backups to the destination site203 using backup or other secondary copy data, the production site 201is not burdened with the synchronization operations. Because thedestination site 203 can be maintained in a synchronized “warm” state,the downtime for switching over from the production site 201 to thedestination site 203 is substantially less than with a typical restorefrom secondary storage. Thus, the production site 201 may flexibly andefficiently fail over, with minimal downtime and with relativelyup-to-date data, to a destination site 203, such as a cloud-basedfailover site. The destination site 203 can later be reversesynchronized back to the production site 201, such as after repairs havebeen implemented or after the failure has passed.

Integrating With the Cloud Using File System Protocols

Given the ubiquity of cloud computing, it can be increasingly useful toprovide data protection and other information management services in ascalable, transparent, and highly plug-able fashion. FIG. 2B illustratesan information management system 200 having an architecture thatprovides such advantages, and incorporates use of a standard file systemprotocol between primary and secondary storage subsystems 217, 218. Asshown, the use of the network file system (NFS) protocol (or any anotherappropriate file system protocol such as that of the Common InternetFile System (CIFS)) allows data agent 242 to be moved from the primarystorage subsystem 217 to the secondary storage subsystem 218. Forinstance, as indicated by the dashed box 206 around data agent 242 andmedia agent 244, data agent 242 can co-reside with media agent 244 onthe same server (e.g., a secondary storage computing device such ascomponent 106), or in some other location in secondary storage subsystem218.

Where NFS is used, for example, secondary storage subsystem 218allocates an NFS network path to the client computing device 202 or toone or more target applications 210 running on client computing device202. During a backup or other secondary copy operation, the clientcomputing device 202 mounts the designated NFS path and writes data tothat NFS path. The NFS path may be obtained from NFS path data 215stored locally at the client computing device 202, and which may be acopy of or otherwise derived from NFS path data 219 stored in thesecondary storage subsystem 218.

Write requests issued by client computing device(s) 202 are received bydata agent 242 in secondary storage subsystem 218, which translates therequests and works in conjunction with media agent 244 to process andwrite data to a secondary storage device(s) 208, thereby creating abackup or other secondary copy. Storage manager 240 can include apseudo-client manager 217, which coordinates the process by, among otherthings, communicating information relating to client computing device202 and application 210 (e.g., application type, client computing deviceidentifier, etc.) to data agent 242, obtaining appropriate NFS path datafrom the data agent 242 (e.g., NFS path information), and deliveringsuch data to client computing device 202.

Conversely, during a restore or recovery operation client computingdevice 202 reads from the designated NFS network path, and the readrequest is translated by data agent 242. The data agent 242 then workswith media agent 244 to retrieve, re-process (e.g., re-hydrate,decompress, decrypt), and forward the requested data to client computingdevice 202 using NFS.

By moving specialized software associated with system 200 such as dataagent 242 off the client computing devices 202, the illustrativearchitecture effectively decouples the client computing devices 202 fromthe installed components of system 200, improving both scalability andplug-ability of system 200. Indeed, the secondary storage subsystem 218in such environments can be treated simply as a read/write NFS targetfor primary storage subsystem 217, without the need for informationmanagement software to be installed on client computing devices 202. Asone example, an enterprise implementing a cloud production computingenvironment can add VM client computing devices 202 without installingand configuring specialized information management software on theseVMs. Rather, backups and restores are achieved transparently, where thenew VMs simply write to and read from the designated NFS path. Anexample of integrating with the cloud using file system protocols orso-called “infinite backup” using NFS share is found in U.S. PatentApplication No. 62/294,920, entitled “Data Protection Operations Basedon Network Path Information.” Examples of improved data restorationscenarios based on network-path information, including using storedbackups effectively as primary data sources, may be found in U.S. PatentApplication No. 62/297,057, entitled “Data Restoration Operations Basedon Network Path Information.”

Highly Scalable Managed Data Pool Architecture

Enterprises are seeing explosive data growth in recent years, often fromvarious applications running in geographically distributed locations.FIG. 2C shows a block diagram of an example of a highly scalable,managed data pool architecture useful in accommodating such data growth.The illustrated system 200, which may be referred to as a “web-scale”architecture according to certain embodiments, can be readilyincorporated into both open compute/storage and common-cloudarchitectures.

The illustrated system 200 includes a grid 245 of media agents 244logically organized into a control tier 231 and a secondary or storagetier 233. Media agents assigned to the storage tier 233 can beconfigured to manage a secondary storage pool 208 as a deduplicationstore, and be configured to receive client write and read requests fromthe primary storage subsystem 217, and direct those requests to thesecondary tier 233 for servicing. For instance, media agents CMA1-CMA3in the control tier 231 maintain and consult one or more deduplicationdatabases 247, which can include deduplication information (e.g., datablock hashes, data block links, file containers for deduplicated files,etc.) sufficient to read deduplicated files from secondary storage pool208 and write deduplicated files to secondary storage pool 208. Forinstance, system 200 can incorporate any of the deduplication systemsand methods shown and described in U.S. Pat. No. 9,020,900, entitled“Distributed Deduplicated Storage System,” and U.S. Pat. Pub. No.2014/0201170, entitled “High Availability Distributed DeduplicatedStorage System.”

Media agents SMA1-SMA6 assigned to the secondary tier 233 receive writeand read requests from media agents CMA1-CMA3 in control tier 231, andaccess secondary storage pool 208 to service those requests. Mediaagents CMA1-CMA3 in control tier 231 can also communicate with secondarystorage pool 208, and may execute read and write requests themselves(e.g., in response to requests from other control media agentsCMA1-CMA3) in addition to issuing requests to media agents in secondarytier 233. Moreover, while shown as separate from the secondary storagepool 208, deduplication database(s) 247 can in some cases reside instorage devices in secondary storage pool 208.

As shown, each of the media agents 244 (e.g., CMA1-CMA3, SMA1-SMA6,etc.) in grid 245 can be allocated a corresponding dedicated partition251A-251I, respectively, in secondary storage pool 208. Each partition251 can include a first portion 253 containing data associated with(e.g., stored by) media agent 244 corresponding to the respectivepartition 251. System 200 can also implement a desired level ofreplication, thereby providing redundancy in the event of a failure of amedia agent 244 in grid 245. Along these lines, each partition 251 canfurther include a second portion 255 storing one or more replicationcopies of the data associated with one or more other media agents 244 inthe grid.

System 200 can also be configured to allow for seamless addition ofmedia agents 244 to grid 245 via automatic configuration. As oneillustrative example, a storage manager (not shown) or other appropriatecomponent may determine that it is appropriate to add an additional nodeto control tier 231, and perform some or all of the following: (i)assess the capabilities of a newly added or otherwise availablecomputing device as satisfying a minimum criteria to be configured as orhosting a media agent in control tier 231; (ii) confirm that asufficient amount of the appropriate type of storage exists to supportan additional node in control tier 231 (e.g., enough disk drive capacityexists in storage pool 208 to support an additional deduplicationdatabase 247); (iii) install appropriate media agent software on thecomputing device and configure the computing device according to apre-determined template; (iv) establish a partition 251 in the storagepool 208 dedicated to the newly established media agent 244; and (v)build any appropriate data structures (e.g., an instance ofdeduplication database 247). An example of highly scalable managed datapool architecture or so-called web-scale architecture for storage anddata management is found in U.S. Patent Application No. 62/273,286entitled “Redundant and Robust Distributed Deduplication Data StorageSystem.”

The embodiments and components thereof disclosed in FIGS. 2A, 2B, and2C, as well as those in FIGS. 1A-1H, may be implemented in anycombination and permutation to satisfy data storage management andinformation management needs at one or more locations and/or datacenters.

Distributed Backup Management

As previously described, in some embodiments, a storage manager 140 maymanage or control backup and/or restore operations between computingsystems of a primary storage system 117 and computing systems of asecondary storage system 118. However, in certain embodiments, theamount of communication with the storage manager 140, as well as otheroverhead, during a backup or restore process may limit the number ofclient computing devices 102 that can be supported by the informationmanagement system 100.

FIG. 3 presents one example of a dataflow diagram 300 illustrating theflow of data and metadata within an example embodiment of theinformation management 100 system. As illustrated by the dataflowdiagram 300, the storage manager 140 may provide control messages andmetadata to a client computing device 102, such as a laptop, tablet, ordesktop computing system. The control messages may include, among otherpossibilities, a trigger to initiate backup of the client computingdevice 102. The metadata may include an identity of the secondarystorage computing device to which to provide data for backup, a numberof communication streams available to the client computing device 102, atype of filter to use in selecting data for backup, a type of scanningprocess (for example, a recursive scan) to identify data for backup, andthe like.

Further, the storage manager 140 may provide metadata and controlmessages to the media agent at the secondary storage computing device106 to facilitate the backup process with the client computing device102. The client computing device 102 can provide the data to be backedup to the selected secondary storage computing device 106 along withmetadata that can be used by the media agent to facilitate creating abackup index for indexing the backed up data. The media agent 144 mayprovide the data and index information to a secondary storage device 108at the information management system 100 or to an external storagesystem 302, such as a cloud-based or network-based storage system thatis external to the information management system 100. In someembodiments, the network-based storage system is at least partiallymanaged by a separate entity or organization than the informationmanagement system 100.

As can be ascertained from the above description of the dataflow diagram300, the backup process is reliant on communication with the storagemanager 140. Further, the media agent at the secondary storage computingdevice 106 is also relied upon during the backup process. For a singleclient computing device 102, the overhead caused by the communicationwith the storage manager 140 and the media agent at the secondarystorage computing device 106 during the backup process may be virtuallynon-existent or at least undetectable by a user of the informationmanagement system 100. However, when it is desired for the informationmanagement system 100 to support thousands, tens of thousands, hundredsof thousands, or even more client computing systems, the overhead causedby communicating with the storage manager 140 and the media agent at thesecondary storage computing device 106 can become a bottleneck that isreadily noticeable by users and reduces the ability of the informationmanagement system 100 to support all of the desired client computingsystems.

FIG. 4 presents an alternative example of a dataflow diagram 400illustrating the flow of data and metadata within an informationmanagement system 100 that reduces overhead compared to the dataflow ofFIG. 3 enabling an increase in scale for the information managementsystem 100. As illustrated by the dataflow diagram 400, the storagemanager 140 may provide control messages to a client computing device102, such as a laptop, tablet, or desktop computing system. Further,like with the dataflow of FIG. 3, the storage manager 140 can providemetadata to the client computing device 102. However, in contrast to theflow illustrated in FIG. 3, the client computing device 102 may storethe metadata in a job cache 402 for use with future jobs. The clientcomputing device 102 may receive a job identifier (e.g., a WorkQToken)from the storage manager 140. This job identifier may be associated withthe metadata at the job cache 402 and can be used to perform additionaljobs without further accessing the storage manager 140. Thus, from theperspective of the storage manager, the subsequent jobs performed by theclient computing device 102 may appear to be one long-running job orpseudo-job.

As with the dataflow of FIG. 3, the storage manager 140 may providemetadata and control messages to the media agent at the secondarystorage computing device 106 to facilitate the backup process with theclient computing device 102. However, in contrast to the dataflow ofFIG. 3, the client computing device 102 may include a core media agentthat provides at least partial functionality of the media agent 144 atthe secondary storage computing device 106. In some such embodiments,the client computing device 102 can communicate data directly to thenetwork storage system 302 without provided the data to the secondarystorage computing device 106. The client computing device 102 mayprovide metadata to the secondary storage computing device 106 that canbe used by the media agent to facilitate creating a backup index forindexing the backed up data. This backup index may be a distributedindex that is distributed among multiple media agents. Alternatively, orin addition, the backup index may be replicated among multiple mediaagents. Advantageously, in certain embodiments, by reducing thefrequency of communication with the storage manager 140 and by enablingthe client computing device 102 to communicate the data directly to thenetwork storage system 302 while providing only the backup metadata tothe secondary storage computing device 106, the overhead of theinformation management system 100 may be reduced enabling theinformation management system 100 to support a greater number of clientcomputing devices 102 with the same amount of computing resources.

Example Distributed Backup Management System

FIG. 5A is a block diagram illustrating some salient portions of asystem 500 for reducing a management burden on a storage managerenabling an increase in scale of clients supported by an informationmanagement system, according to an illustrative embodiment of thepresent invention. In some embodiments, the system 500 can be part of aninformation management system 100 and may include one or more of thesystems and one or more of the embodiments previously described withrespect to the information management system 100. For ease ofillustration and to simplify the related discussion, the system 500illustrates a single client computing device 102 and a single secondarystorage computing device 106. However, it should be understood thatgenerally there are multiple client computing devices 102 and multiplesecondary storage computing devices 106. For example, there may be20,000, 50,000, or 250,000 client computing devices 102 included as partof the primary storage subsystem 117. Further, there may be 10 s, 100 s,or thousands of secondary storage computing devices 106. In addition,there may be multiple storage managers 140. For example, the informationmanagement system 100 may be divided into different domains with eachdomain being assigned a different storage manager 140 or subset ofstorage managers.

In certain embodiments, a trigger may cause a data agent 142 of theclient computing device 102 to initiate a backup process for backing updata of a primary storage device 104 of the client computing device 102.The client computing device 102 using, for example, the data agent 142may obtain a job identifier and a set of job metadata that identifiesresources available to the client computing device 102 to complete thebackup process. The client computing device 102 may store the jobidentifier and the set of job metadata at a job cache 516. By storingthe job identifier and the set of job metadata at the job cache 516, theclient computing device 102 may perform multiple jobs using the same jobidentifier and the stored set of job metadata. The client computingdevice 102 includes a cache manager 514 for managing the job cache 516.Further, the cache manager 514 can determine whether the job identifier,and associated job metadata, is expired. If the job identifier, or theassociated job metadata, is expired, the data agent 142 can communicatewith the storage manager 140 to obtain a new job identifier and toconfirm the set of job metadata or to obtain updated job metadata.

In some embodiments, the client computing device 102 may include a coremedia agent 510. The core media agent 510 may be a reduced orslimmed-down media agent that includes some of the capabilities of themedia agent 144. For example, the core media agent 510 may be a reducedmedia agent that is capable of migrating data or providing data forbackup to a secondary store, such as at the network storage system 302,but may not have other capabilities of a media agent. For example, thecore media agent 510 may not have features that enable the core mediaagent 510 to generate or maintain an index of the backup or to performdeduplication tasks that may be performable by a full media agent, suchas the media agent 144.

In some embodiments, a media agent 144 can be divided into twosubsystems, a data migration system 504 and a data management system506. The core media agent 510 may include a data migration system 512that can communicate with the network storage system 302, but may notinclude a data management system. On the other hand, the media agent 144within the secondary storage subsystem 118 may include both a datamigration system 504, which may have the same capabilities as the datamigration system 512, and a data management system 506. The datamanagement system 506 may include any system for creating a backup ormedia agent index 153. In some embodiments, the data management system506 may receive information relating to the data or files provided tothe network storage 302 or modified at the network storage 302. The datamanagement system 506 can use the information to create an index thatenables retrieval of the data from the network storage 302. For example,the index may identify where the data is stored at the network storage302, when the data was modified, when the data was provided to thenetwork storage system 302, and the like.

The data migration system 512 can communicate data to be backed up fromthe primary storage device 104 to the network storage system 302 withoutcommunicating the data to a secondary storage computing device 106 inthe secondary storage subsystem 118. For example, the data migrationsystem 512 may cause the client computing device 102 to establish acommunication connection with the network storage system 302. Using thecommunication connection, the client computing device 102 may streamdata for backup to the network storage system 302. Separately, the coremedia agent 510 may provide metadata to the data management system 506relating to the data provided to the network storage 302. Using thismetadata, the data management system 506 can create an index of thebackup that can be used to restore some or all of the backed up data. Insome embodiments, the data management system 506 may access the networkstorage system 302 to complete the backup index generation process. Forexample, the data management system 506 may access the network storagesystem 302 to determine a status or location of data provided to thenetwork storage system 302 for backup. The network storage system 302may store the data in one or more secondary storage devices 526 of thenetwork store system 302, as indicated by the data block 528. In certainembodiments, the core media agent 510 may be a duplicate of the mediaagent 144 and may include the same features as the media agent 144.

The core media agent 510 may provide backup metadata or backup indexinformation to the data management system 506 of the media agent 144.The media agent 144, using the indexing system 502, may generate abackup index at the media agent index 153 that includes informationabout the data stored at the network storage system 302.

In certain embodiments, the indexing system 502 may be included on orimplemented by the secondary storage computing device 106. In certainembodiments, the backup index 153 and/or the metadata index 534 of theindexing system 502 may be stored in a storage device of the secondarystorage computing device 106. Further, the media agent 144 can create atransaction log file 522, which may be one of a plurality of transactionlog files 520 maintained by the secondary storage computing device 106.Each transaction log file 522 may include data that is being backed up.For example, each transaction log file 522 may include a file systemobject with index-able metadata. In some embodiments, each transactionlog file 522 may include attributes of files that have been backed up bythe data migration system 504 or the data migration system 512 to thenetwork storage system 302. The media agent 144 may periodically back upthe transaction log files 522 to the network storage system 302, asindicated by the TLFs 530 stored in the secondary storage devices 526 ofthe network storage system 302. Further, the media agent 144 can backupthe backup index 153 to the network storage system 302, as indicated bythe index 532 at the secondary storage devices 526.

The backup index 153 and the transaction log files 520 may be generatedperiodically or at particular scheduled times. However, in certainembodiments, one or more transactions associated with backing up data tothe network storage system 302 or accessing backed up data from thesecondary storage system 302 may occur at times other than the timeswhen the backup index 153 and/or the transaction log files 520 aregenerated. In some such cases, a transaction identifier for eachperformed transaction may be provided to a metadata index 534. When atrigger causes a transaction log file 522 to be generated, the mediaagent 144 may access the metadata index 534 to identify any transactionsthat may have occurred since the previous transaction log file 522 orthe previous backup index 153 was generated.

FIG. 5B is a block diagram illustrating some salient portions of asystem 575 for reducing a management burden on a storage managerenabling an increase in scale of clients supported by an informationmanagement system, according to an illustrative embodiment of thepresent invention. In certain embodiments, the system 575 includes oneor more of the embodiments described with respect to the system 500.Further, the secondary storage computing device may include an indexingagent 580. The indexing agent 580 may include any system that canperform indexing of a backup or archive. Further, the indexing agent 580can facilitate restore of a backup from a network storage system 302. Incertain embodiments, the indexing agent 580 includes a data managementsystem 506. In certain embodiments, the combination of the core mediaagent 510 and the indexing agent 580 may perform the operations of amedia agent 144. In other words, in certain embodiments, the media agent144 may be divided into a core media agent 510 that can migrate databetween a primary storage device 104 and a network storage 302, and anindexing agent 580 that can create, maintain, and/or update an index fora backup or archive of the primary storage device 104. Advantageously,in certain embodiments, by dividing the media agent 144, and theoperations performed by the media agent 144, across the client computingdevice and the secondary storage computing device, the amount of timespent by the client computing device 102 during a backup process can bereduced. Further, the resource burden, such as bandwidth and the numberof communication connections between the client computing device 102 andthe secondary storage subsystem 118 and/or the network storage 302 maybe reduced.

Additional processes and details of the operations of the systemsillustrated in FIGS. 5A and 5B are described below with respect to FIGS.6 through 10.

Example Client Managed Job Process

FIG. 6 depicts some salient operations of a client managed job process600 according to an illustrative embodiment of the present invention.The process 600 can be implemented by any system that can self-manage ormanage a job, such as a backup of a primary storage device 104, at asecondary storage system 118 without communicating with or with minimalcommunication to the storage manager 140. The process 600, in whole orin part, can be implemented by, for example, a data agent 142, a cachemanager 514, or a job cache repository 516, among others. Although anynumber of systems, in whole or in part, can implement the process 600,to simplify discussion, the process 600 will be described with respectto particular systems.

The process 600 begins at block 602 where, for example, the data agent142 detects a trigger at the client computing device 102 to perform ajob at a secondary storage system. The secondary storage system may beor may include the secondary storage subsystem 118 or a network storagesystem (sometimes referred to as a “cloud” or “cloud storage system”),such as the network storage system 302. The job may include any type ofjob or task that relates to the access or management of data at asecondary storage system 118. Typically, the job is a backup of datafrom a primary storage device 104 to a secondary storage, such as asecondary storage device 108 or a network storage system 302. However,in certain embodiments, the job may include a restore operation torestore data from a secondary storage system 118 or a network storagesystem 302 to a primary storage system 117. Further, the job may includean archiving operation, a de-duplication operation, or any other type ofdata management operation with respect to a secondary storage system 118or a network storage system 302. To simplify discussion, and not tolimit the present disclosure, the job will primarily be described as abackup job unless specified otherwise. It should also be understood thatthe backup job may include different types of backup operations. Forexample, the backup operation may be a complete backup, a backup of asubset of files in a primary storage device 104, a differential backup,or any other type of backup process that may be performed with respectto the primary storage device 104. In some embodiments, the backupoperation may include or may be an archiving operation.

The trigger may include a command received from a user, an administratoruser, another computing device, an occurrence of a defined sequence ofevents (for example, a creation of a particular number of files or amodification in hardware configuration of the client computing device102), or the passage of time. In some cases, the job may be scheduled tobe performed at particular periods of time or at a particular timeintervals. For example, the job may be scheduled to be performed everyweekday, every evening, every week, or once a month. Further, in certainembodiments, the trigger may include a detection of a thresholdpercentage or amount of change in data or files at the primary storagedevice 104.

The client computing device 102 may generally include any type of clientcomputing device. For example, the client computing device may be alaptop, a tablet, a desktop computing system, a smart phone, a computingkiosk, a smart appliance, or any other type of computing system.Typically, the client computing device is one of a large number ofcomputing devices at an entity or organization. For example, the clientcomputing device may be one of 100 or 200,000 computing devices.Although generally the computing device is a client computing device, insome embodiments, the computing device may be a server computing device.

At decision block 604, the data agent 142 determines whether an activejob identifier exists for the client computing device 102. Determiningwhether an active job identifier exists may include determining whetherthe job identifier available to the client computing device 102 hasexpired. The job identifier may be provided by a storage manager 140 fora single job. However, in embodiments of the present disclosure, theclient computing device 102 may use the job identifier for multiplejobs. Advantageously, in certain embodiments, by reusing the jobidentifier for multiple jobs, communication with the storage manager 140may be reduced, thereby reducing the burden on the storage manager 140and enabling the storage manager 140 to manage a greater number ofcomputing systems. In certain embodiments, when the client computingdevice 102 performs multiple jobs using the same job identifier, thestorage manager 140 may process the multiple jobs as a single jobassociated with the same job identifier.

If it is determined at the decision block 604 that an active jobidentifier does not exist for the client computing device 102, the dataagent 142 requests a job identifier from the storage manager 140 atblock 606. The block 606 may include providing information about theclient computing device 102, such as the size of the primary storagedevice 104, the amount of data on the primary storage device 104, aspeed or capability of a network card included in the client computingdevice 102, or any other information that may affect the performance ofthe job by the client computing device 102. In some embodiments, theblock 606 may include providing information about the job to beperformed to the storage manager 140. For example, the block 606 mayinclude identifying to the storage manager 140 that the job is a backupjob or restore job. Further, the block 606 may include informing thestorage manager 140 of the amount of data to be backed up or restored.

At block 608, the data agent 142 receives a job identifier and relatedjob metadata from the storage manager 140. The job metadata may includea designation of computing resources allotted to or available to theclient computing device 102 to perform the job. For example, the jobmetadata may identify a number of communication streams designated forthe client computing device 102 to communicate with the secondarystorage system 118 or the network storage system 302. As anotherexample, the job metadata may include an identity of a particularsecondary storage computing device 106 or a particular media agent 144for the client computing device 102 to communicate with to perform thejob. In addition, the job metadata may identify filters to be used bythe client computing device 102 and selecting data or files at theprimary storage device 104 to backup. In some cases, the job metadatamay also identify a type of scan to perform to identify data to back up.For example, the type of scan may be a recursive scanning algorithm oran iterative scanning algorithm. In some embodiments, the job metadatamay include a job identifier, an archive identifier, a chunk identifier,a job token, and the like. In some embodiments, a job identifier may berelated to an archive identifier and/or a chunk identifier. Theseidentifiers may be used to identify data to prune or restore from abackup.

In some systems, a client device may incur many jobs (e.g., hundreds,thousands, or more), which may result in many archive identifiers andcorrespondingly fragmented chunks associated with the jobs. The manychunks, archive identifiers, and other tracking and management data cansignificantly increase an amount of resources required for datamanagement and generally system book-keeping. Further, the many chunks,archive identifiers, and other tracking and management data can addcomplexity to restore and pruning operations.

On the other hand, by having a relatively large archive, it is easier tomanage jobs and overall efficiency for restoring and pruning operationscan be increased while computing resources for book-keeping or othertracking and management operations can be reduced. Thus, reusing a jobidentifier and/or archive identifier for multiple jobs can reducecomputing resources used for management tasks. The job identifier and/orarchive identifier can be reused for multiple jobs for a particular timeperiod and/or until a backup or archive reaches a particular size. Theparticular size and/or time period may be configurable. Once the timeperiod or size is reached, the job identifier or archive identifier maybe rotated. In certain embodiments, the identifiers may be rotated ifthere is an error at the information manager relating to archive orchunk management relating to a particular job.

At block 610, the cache manager 514 stores the job identifier and therelated job metadata that the job cache 516. In certain embodiments, theclient computing device 102 may be configured with particular defaultjob metadata. For example, the client computing device 102 may bydefault perform recursive scanning. In some such embodiments, the jobmetadata received from the storage manager may be complementary to thedefault job metadata and/or may replace some of the default jobmetadata. Storing the related job metadata at the job cache 516 mayinclude associating the related job metadata with the job identifier atthe job cache 516.

At block 612, the data agent 142 performs the job using the jobmetadata. Further, the data agent 142 may associate the job with the jobidentifier. Performing the job using the job metadata may includeperforming or initiating a backup process using the computing and/orcommunication resources available to the client computing device 102 asidentified by the job metadata.

If it is determined at the decision block 604 that an active jobidentifier does exist for the client computing device 102, the dataagent 142, using the cache manager 514, accesses job metadatacorresponding to the job identifier from the job cache 516. Using thejob metadata accessed from the job cache 516, the data agent 142 maydetermine resources available to complete the job. By using the storedjob metadata to perform multiple jobs and by associating the multiplejobs with the same job identifier, communication with the storagemanager 140 is reduced enabling the storage manager 140 to support moredevices.

At block 616, the data agent 142 performs the job using the job metadatawithout obtaining a new job identifier. Further, the data agent 142 mayassociate the job with the job identifier, which may previously havebeen associated with previously performed jobs. In some embodiments, thedata agent 142 may assign another identifier to the job that isassociated with the job identifier. For example, the data agent 142 mayassign a sub-identifier or a set of nested identifiers to each job thatis associated with the job identifier previously provided by the storagemanager 140. By assigning a sub-identifier or other identifier that isassociated with the job identifier to the job, the client computingdevice 102 can uniquely identify each particular job associated with thesingle job identifier provided by the storage manager 140.

Example Job Metadata Update Process

FIG. 7 depicts some salient operations of a job metadata update process700 according to an illustrative embodiment of the present invention.The process 700 can be implemented by any system that can update jobmetadata at one or more client computing devices. The process 700, inwhole or in part, can be implemented by, for example, a storage manager140, a jobs agent 156, or a management agent 154, among others. Althoughany number of systems, in whole or in part, can implement the process700, to simplify discussion, the process 700 will be described withrespect to particular systems.

The process 700 begins at block 702 where, for example, the storagemanager 140 determines a change at the information management system 100affecting job metadata. The change at the information management system100 may include any type of change that modifies the resources availableto one or more computing devices within the primary storage system 117.In some embodiments, the change in resources available may be a changeto resources available within the primary storage system 117, a changein resources available in the secondary storage system 118, or changein's resources available at the network storage system 302. Somenon-limiting examples of changes at the information management systemthat can affect the job metadata may include the addition of or the lossof access to a media agent 144 or a secondary storage computing device106, a change in the availability of one or more secondary storagedevices 108, a change in the amount of storage available at thesecondary storage system 118 or at the network storage system 302, achange in the number of communication streams or the bandwidth of thecommunication streams available at the information management system100, a change in the availability of network resources, a change in thepriority level or access control level of one or more systems of theinformation management system 100, a change in the number of clientcomputing devices 102 requesting access to resources at the informationmanagement system 100, or any other change that may affect theavailability of resources that may be available to perform a job.

At block 704, the storage manager 140 identifies one or more clientcomputing devices 102 provided with outdated or expired job metadata. Insome embodiments, the block 704 may include identifying all clientcomputing devices 102 within the information management system 100 thathave been provided with job metadata. In other embodiments, the block704 may include identifying a subset of client computing devices 102that may be designated or selected to receive an modified amount ofcomputing resources as determined by an administrator or an allocationalgorithm performed by the storage manager 140. In some embodiments, theblock 704 may include identifying a subset of client computing devices102 that are associated with an unexpired job identifier.

At block 706, the storage manager 140 updates the job metadata for theone or more client computing devices 102 based on the change at theinformation management system 100. In some embodiments, updating the jobmetadata for the one or more client computing devices 102 may includemodifying the job metadata previously provided to the one or more clientcomputing devices 102 based on the change in the information managementsystem 100. In some embodiments, different client computing devices 102may be updated with different job metadata. In some embodiments some ofthe client computing devices 102 may be updated with different jobmetadata and other client computing devices 102 may not be updated ormay not be assigned updated job metadata. In some embodiments, thestorage manager 140 may determine job metadata to provide, or computingresources to assign, to one or more client computing devices 102 basedon the current state or configuration of the information managementsystem 100. In some such cases, the storage manager 140 may determinethe computing resources were job metadata to provide to the one or moreclient computing devices 102 without accessing or considering prior jobmetadata provided to the one or more client computing devices 102.

At block 708, the storage manager 140 provides the one or more clientcomputing devices 102 with the updated job metadata. Providing a clientcomputing device 102 with the updated job metadata may include providinga new job identifier to the client computing device 102 associated withthe updated job metadata. Alternatively, providing the client computingdevice 102 with the updated job metadata may include identifying to theclient computing device 102 an associated job identifier previouslyprovided to the client computing device 102 enabling the clientcomputing device 102 to modify the job metadata associated with thepreviously provided job identifier.

In certain embodiments, the updated job metadata is pushed to the clientcomputing device 102. In other words, in certain embodiments, thestorage manager 140 may provide the updated job metadata to the clientcomputing device 102 without the client computing device 102 requestingthe updated job metadata. Upon receiving the updated job metadata, thecache manager 514 of the client computing device 102 may update the jobcache 516 to store the updated job metadata. Updating the job cache 516to store the updated job metadata may include associating the updated tometadata with a new job identifier at the job cache 516 or with apreviously provided job identifier at the job cache 516.

Example Backup Process

FIG. 8 depicts some salient operations of a backup process 800 accordingto an illustrative embodiment of the present invention. The process 800can be implemented by any system that can perform a backup process forbacking up a primary storage device 104 to a secondary storage or anetwork storage system. The process 800, in whole or in part, can beimplemented by, for example, a client computing device 102, a data agent142, a core media agent 510, a data migration system 512, a media agent144, a data migration system 504, or a data management system 506, amongothers. Although any number of systems, in whole or in part, canimplement the process 800, to simplify discussion, the process 800 willbe described with respect to particular systems. Further, although theprocess 800 is primarily described with respect to backing up a primarystorage device 142 network store system 302, in some embodiments, theprocess 800 or a modified version of the process 800 may be used toperform a restore process for restoring data from a network storagesystem 302 to a primary storage device 104 of the client computingdevice 102.

The process 800 begins at block 802 where, for example, the data agent142 detecting a trigger at a client computing device 102 to perform abackup of a primary storage device 104 at a network storage system 302.The trigger may include a command received from a user, an administratoruser, another computing device, an occurrence of a defined sequence ofevents (for example, a creation of a particular number of files or amodification in hardware configuration of the client computing device102), or the passage of time. In some cases, the backup job may bescheduled to be performed at particular periods of time or at particulartime intervals. For example, the job may be scheduled to be performedevery weekday, every evening, every week, or once a month. Further, incertain embodiments, the trigger may include a detection of a thresholdpercentage or amount of change in data or files at the primary storagedevice 104.

At block 804, the cache manager 514 accesses the job cache 516 to obtainjob metadata. Accessing the job cash 516 may include identifyingparticular job metadata associated with a currently pending, active, ornon-expired job identifier. In some embodiments, the job identifier maybe used as an index into the job cache 516 to identify current ornon-expired job metadata associated with the job identifier.

At decision block 806, the data agent 142 determines whether the clientcomputing device 102 is capable of interacting with the network storagesystem 302. In certain embodiments, determining whether the clientcomputing device 102 is capable of interacting with the network storagesystem 302 is based at least in part on the job metadata obtained at theblock 804. In other embodiments, determining whether the clientcomputing device 102 is capable of interacting with the network storagesystem 302 is performed without consideration of job metadata stored atthe job cache 516. In some such embodiments, the block 804 may beoptional or omitted.

In some embodiments, the decision block 806 may include determiningwhether the client computing device 102 is authorized to access thenetwork storage system 302. Determining whether the client computingdevice 102 is authorized to access the network store system 302 mayinclude determining whether the client computing device 102 has anaccount with the network storage system 302 or has authorizationinformation, such as a username and/or password for accessing thenetwork storage system 302. In some embodiments, the decision block 806may include attempting to communicate with the network storage system302 to confirm whether the client computing device 102 is capable ofinteracting with the network storage system 302. Attempting tocommunicate with the network storage system 302 may include sending atest communication packet to the network storage system 302, attemptingto authenticate with the network store system 302, or performing anyother operation that may confirm whether the client computing device 102is capable of interacting with the network storage system 302. In someembodiments, the decision block 806 may include requesting access to thenetwork storage system 302 from one or more of the storage manager 140,the network storage system 302, or a secondary storage computing device106.

If it is determined at the decision block 806 that the client computingdevice 102 is capable of interacting with the network storage system302, the data agent 142 provides data to the core media agent 510 at theclient computing device 102. The data provided to the core media agent510 includes a data from the primary storage device 104 to be backed up.This data may include one or more files, directories, metadata, or othertypes of data to be backed up. Providing the data to the core mediaagent 510 may include providing the core media agent 510 with access tothe data at the primary storage device 104. In certain embodiments,providing the data to the core media agent 510 may include copying thedata from the primary storage device 104 to a memory location at theclient computing device 102 that is accessible to the core media agent510. This memory location may, for example, be volatile memory ornon-volatile memory that is assigned to the core media agent 510 or toone or more process threads of the core media agent 510.

At block 810, the core media agent 510 backs up the data at the networkstorage system 302 without accessing the media agent 144 at thesecondary storage system 118. Backing up the data at the network storesystem 302 may include communicating the data to the network storagesystem 302 directly or via a network, such as, but not limited to, theInternet. Advantageously, in certain embodiments, by providing the datafor backup to the core media agent 510 and by backing up the data at thenetwork store system 302 without communicating the data to the secondarystorage system 118 or to the media agent 144, the amount of processingperformed by the media agent 144 during a backup process is reduced. Byreducing the processing or overhead of the media agent 144, the mediaagent 144 and/or the secondary storage computing device 106 may supporta larger number of client computing devices 102 enabling the informationmanagement system 100 to be scaled to support more client computingdevices 102. Further, in certain embodiments, by reducing the overheadon the media agent 144 during the backup process, information managementsystem 100 can support an increased rate of occurrence of the backupprocess. In other words, in certain embodiments, the client computingdevice 102 may be backed up more frequently due to the reduced burden onthe secondary storage system 118 by performance of the process 800 andthe communication of data for backup directly to the network storagesystem 302 instead of the of the secondary storage system 118.

If it is determined at the decision block 806 that the client computingdevice 102 is not capable of interacting with the network storage system302, the data agent 142 provides data for backup to the media agent 144at the secondary storage computing device 106 of the secondary storagesystem 118. Providing the data for backup to the media agent 144 mayinclude streaming data from the primary storage device 104 to the mediaagent 144 or to the secondary storage computing device 106.

At block 814, the data agent 142 backs up the data at the networkstorage system 302 using the media agent 144 at the secondary storagesystem 118. Backing up the data to the network storage system 302 mayinclude streaming the data from the secondary storage computing device106 to the network storage system 302. In some embodiments, the block814 is performed by the media agent 144. In some embodiments, the blocks810 and 814 may include backing up the data to a secondary storagedevice 108 instead of or in addition to backing up the data to thenetwork storage system 302. In such embodiments, the block 810 mayinclude backing up the data to the secondary storage device 108 withoutaccessing the media agent 144 or the secondary storage computing device106.

At block 816, the media agent 144 generates a backup index at thesecondary storage system 118. In certain embodiments, regardless ofwhether the backup is performed by the media agent 144 or the core mediaagent 510, the backup index may be generated by the media agent 144 atthe secondary storage system 118. As previously described, the backupindex may be a media agent index 153 and may include a data structurethat includes information about the stored data. In some embodiments, aspreviously described, the media agent index 153 may store informationabout stored data associated with a particular media agent 144. However,in other embodiments, the media agent index 153 may not be associatedwith a particular media agent 144 and may be distributed among a set ofmedia agents 144. Moreover, as the data may be backed up to the networkstorage system 302 instead of the secondary storage system 118, themedia agent index 153 generated by the media agent 144 may be associatedwith one or more particular backups of data at the network storagesystem 302. The media agent index 153 generated by the media agent 144may facilitate searching and accessing data backed up to the networkstorage system 302. In certain embodiments, generating the backup indexmay include performing one or more operations of the process 900described with respect to FIG. 9.

At block 818, the media agent 144 stores the backup index at thesecondary storage system 118. In certain embodiments, the block 818 mayinclude backing up the backup index, or the media agent index 153, tothe network storage system 302. Further, in certain embodiments, theblock 818 may include distributing the backup index among a plurality ofmedia agents 144.

Example Indexing Process

FIG. 9 depicts some salient operations of an indexing process 900according to an illustrative embodiment of the present invention. Theprocess 900 can be implemented by any system that can perform anindexing process for creating a backup index to facilitate access todata stored or backed up to a secondary storage system 118 or a networkstorage system 302. The process 900, in whole or in part, can beimplemented by, for example, a media agent 144, a data management system506, a secondary storage computing device 106, a storage manager 140, oran indexing system 502, among others. Although any number of systems, inwhole or in part, can implement the process 900, to simplify discussion,the process 900 will be described with respect to particular systems.

The process 900 begins at block 902 where, for example, the media agent144, using the data management system 506, generates a backup indexbased at least in part on the backup metadata corresponding to a backupjob. This backup metadata may be received from the client computingdevice 102, the core media agent 510, or the data agent 142. In someembodiments, the block 902 may include storing the backup index at theindexing system 502. The backup job may be a full backup of the primarystorage device 104. Further, in certain embodiments the backup job maybe an initial backup of the primary storage device 104. In otherembodiments, the backup job may be any type of backup or archive theprimary storage device 104 and may or may not be an initial backup ofthe primary storage device 104 to stop

At block 904, the media agent 144 backs up the backup index to a networkstorage system 302. Backing up the backup index to the network storagesystem 302 may include associating the backup index with the backup job.This backup job may be a backup job performed by the media agent 144 ora backup job performed by the core media agent 510. In other words, incertain embodiments, the backup index generated by the media agent 144may be associated with a backup job is performed by system other thanthe media agent 144, such as the core media agent 510. In some suchembodiments, despite not receiving the data for backup, the media agent144 may generate the backup index based on backup metadata received fromthe core media agent 510, the data agent 142, or the client computingdevice 102.

At block 906, the media agent 144 receives a set of transaction logfiles including metadata corresponding to a job performed by a client.This job may be a separate or subsequent job to the job that generatedthe metadata used to create the backup index at the block 902. Further,the metadata received at the block 906 may be received over time or overa set of time intervals. For example, a first set of metadata may bereceived at or during a first time period while a second set of metadatamay be received at or during a second time period that is later than thefirst time period. The second set of metadata may come in some cases, bereceived after a period of inactivity following receipt of the first setof metadata. In certain embodiments, the metadata received at the block906 may be received at the same time as or substantially in parallel tothe corresponding job being performed by the client computing device 102or the media agent 144.

At block 910, the media agent 144 backs up the set of transaction logfiles at the network storage system 302. Backing up the set oftransaction log files may include storing the data and, in some cases,the metadata at the network storage system 302 without updating orgenerating a backup index associated with the data of the transactionlog files. In some embodiments, the set of transaction log files may bebacked up to the network storage system 302 as they are received orcreated during the set of time intervals. In other embodiments, the setof transaction log files may be aggregated and backed up to the networkstorage system 302 together during a particular period in time. In someembodiments, the block 910 may include distributing the set oftransaction log files 522 across a plurality of media agents 144 or aplurality of secondary storage computing devices 106. The set oftransaction log files 522 may be backed up periodically. For example,the set of transaction log files 522 may be backed up once a day, everytwo hours, or each workday. In certain embodiments, the transaction logfiles 522 are backed up more frequently than the backup index. Thus, forexample, while the backup index may be backed up to the network storagesystem 302 once a day or once a week, the transaction log files 522 maybe backed up each hour or a few times a day.

Generally, storing the attributes of files or data and/or thetransaction log file 522 is faster than generating a backup index. Thus,in certain embodiments, attributes of files or data obtained from themetadata received at the block 906 may be stored in a transaction logfile 522 during a time period while a job is occurring. At some periodof time subsequent to the backup job completing, a backup index can begenerated based on the set of transaction log files. Advantageously, incertain embodiments, by first storing file data attributes in atransaction log file 522 and later generating the backup index, theamount of time required to complete the backup process, or the man oftime that the client computing device 102 is involved in the backupprocess, may be reduced.

A backup index may be implemented as a database. Storing and/ormaintaining the backup index separately from the TLF(s) can have severalbenefits. One advantage is that it is possible to transition the backupindex to a new or different storage technology with or without anychanges to the TLFs or backed up data. For example, a common or middlelayer may be implemented between the backup index and the TLFs. Themiddle layer could translate the TLFs to the new database schemaassociated with the new backup index technology or vice versa. Further,in certain embodiments, by separating the TLFs from the backup indexing,it is possible to store the TLFs and to generate or update the backupindex at a later time, such as when more computing resources areavailable. Thus, in certain embodiments, scheduled backup indexes can besatisfied even when a system is busy because, for example, the amount ofcomputing resources required to complete the backup can be reduced byseparating when the storage of the TLFs and the generation of the backupindex occurs. Further, the TLFs can be used to regenerate a backup indexif there is loss of a previously generated backup index.

Moreover, in certain cloud backup or network storage embodiments, adistributed backup process comprising backing up the TLFs in networkstorage at a first time period and later playing back the TLF at asecond time period to generate the backup index can have significantscale and performance improvements. For example, a large number of TLFscan be stored at a first time period using a set of available networkcomputing resources. At a second time period when a greater amount ofcomputing resources are available or when the cost of using thecomputing resources is lower, the backup index can be created reducing aburden on available computing resources and/or reducing cost.

In certain embodiments, one transaction log file 522 may be generatedfor each job performed by the client computing device 102. In otherembodiments, multiple transaction log files 522 may be generated per jobperformed by the client computing device 102. The transaction log files522 may include attributes of files or data that are included as part ofthe backup process.

At block 912, the media agent 144 generates a transaction metadata indexat the indexing system 502 to manage the transaction log files 522 for aset of media agents. The transaction metadata index may be distributedamong a plurality of media agents 144. Advantageously, in certainembodiments, by distributing or replicating the indexing system 502among a plurality of media agents 144 and/or secondary storage computingdevices 106, access to the backup index 153 and the transaction logfiles 522 may be maintained when some of the media agents 144 orsecondary storage computing devices 106 suffer or experience a failure.

At block 914, the media agent 144 updates a backup index 153 based atleast in part on the set of transaction log files 522. In certainembodiments, updating the backup index 153 may include generating a newbackup index based at least in part on the set of transaction log files522. In some cases, the new backup index may be generated based on theprevious backup index 153 generated at the block 902. A TLF 522 mayinclude the backed up data and index-able metadata. Updating the backupindex can include executing or performing one or more commands oractions based on the data stored in the transaction log files to bringthe backup index and indexing information in the backup index repositoryup-to-date based on the data that has been backed up.

At block 916, the media agent 144 backs up the updated backup index tothe network storage system 302. Backing up the updated backup index tothe network storage system 302 may include modifying the backup indexpreviously stored to the network store system 302. Alternatively, or inaddition, backing up the updated backup index may include storing a newcopy of a backup index corresponding to the updated backup index to thenetwork storage system 302.

At block 918, the media agent 144 stores a transaction identifier, or atransaction number, for each transaction occurring subsequent to storageof the most recent transaction log file 522 in a metadata index 534.Storing the transaction log file 522 in the metadata index 534 mayinclude storing metadata of the transaction log file 522, or of datastored in the transaction log file 522, in the metadata index 534. Insome embodiments, the transaction identifiers for each transactionoccurring subsequent to storage of the most recent transaction log filemay be stored at the network storage system 302. Further, in someembodiments, upon a particular number of transaction identifiers beingstored or upon a particular point in time being reached, a newtransaction log file may be generated based on the transactionidentifiers. In some such cases the transaction identifiers may bediscarded upon creation of the new transaction log file. Further,additional transaction identifiers associated with transactionsoccurring subsequent to the new transaction log file 522 may becollected and stored at the metadata index 534.

In certain embodiments, the transaction number may be a serial numberassociated with a client device that is backed up. Each client devicemay be associated with a different transaction number. A transaction logfile that is generated during a backup process may be named after thetransaction number. In certain embodiments, each transaction that isgenerated during the backup process may be recorded in an index, such asthe backup index 153, the metadata index 534, or the index 532. When atransaction is consumed or recorded into the index, an attribute, flag,or other marker may be recorded representing that transaction in theindex. This attribute may indicate that the transaction is consumed orrecorded. Periodically, it can be checked whether all receivedtransactions have been consumed or not by checking the flag in theindex. If it is determined that any unconsumed transactions exist, thetransaction can be retried, and the index can be updated to indicatethat the transaction metadata has been recorded in the index.

The process 900, or portions thereof may be repeated intermittently, ona continuous basis, or each time a backup job is performed. For example,the operations associated with the blocks 906-910 may be repeated for aparticular number of jobs. In some embodiments, after a particularnumber of jobs, the process 900 may return to the block 902 to create anew backup index. Thus, in one non-limiting example, a backup index maybe created at time 0. At times 10, 20, 30, and 40, a set of transactionlog files may be created. At times occurring between the creation of thebackup index and/or each transaction log file, transaction identifiersfor each transaction occurring in the time intervals may be stored. Forexample, transaction identifiers for transactions occurring betweentimes 10 and 20 may be stored at the metadata index 534. Metadataassociated with these transactions may then be integrated or included aspart of the transaction log file created at time 20. At time 50, a newbackup index may be created, or the backup index generated at time 0 maybe updated based on the transaction log files created at times 10, 20,30, and 40. The backup index may also be updated based on transactionsoccurring between time 40 and 50. At time 60, a number transaction logfile may be generated.

As will be understood from the previous description, the process 900 maybe a form of tiered indexing process that creates different types orgranularities of indexes. In certain embodiments, at least some of theoperations associated with the process 900 may be performed in adifferent order or at least partially in parallel. For example, in someembodiments, a backup index may be created prior to the formation oftransaction log files. In some other embodiments, transaction log filesmay be created first, and a backup index may be created later, with orwithout using the transaction log files.

Example Media Agent Restoration Process

FIG. 10 depicts some salient operations of a media agent restorationprocess 1000 according to an illustrative embodiment of the presentinvention. The process 1000 can be implemented by any system that canadd a new media agent to a secondary storage system 118 or replace amedia agent at the secondary storage system 118. The process 1000, inwhole or in part, can be implemented by, for example, a storage manager140 or a secondary storage computing device 106, among others. Althoughany number of systems, in whole or in part, can implement the process1000, to simplify discussion, the process 1000 will be described withrespect to particular systems.

The process 1000 begins at block 1002 where, for example, the storagemanager 140 detects a failure of the media agent 144 at the secondarystorage system 118. In some embodiments, the block 1002 may be optionalor omitted. For example, in some embodiments, the process 1000 may beused to add new or additional media agents 144 to the secondary storagesystem 118 when, for example, scaling the information management system100 to provide additional computing resources or support additionalclient computing devices 102. In such embodiments, the process 1000 maybe performed without the detection of a failure of a media agent 144.

Alternatively, or in addition, the block 1002 may detect that a newmedia agent should be configured or made available based on one or moredetected scaling criteria associated with the information managementsystem 100. In some cases, the media agent may be added if the detectedscaling criteria satisfy a scaling threshold. This scaling criteriaand/or threshold may relate to the number of computing devices availableor registered at the primary storage system 117, the amount of expectedbackups to be performed, the amount of data to be backed up, or anyother criteria that may affect the number of media agents to be used.For example, if the storage manager 140 detects that more than athreshold number of client computing devices have been added to orregistered with the primary storage system 117, the storage manager 140may determine that one or more additional media agents should beconfigured or made available to the information management system 100,to the primary storage system 117, or to the secondary storage system118. As another example, if it is determined that a threshold number ofbackup operations are to be scheduled over a particular time period, thestorage manager 140 may determine that one or more additional mediaagents should be configured or made available. In certain embodiments,the failure of one or more media agents may cause the scaling criteriato satisfy a scaling threshold that causes the storage manager 140 toconfigure new or additional media agents. In some cases, the failure ofone media agent may not cause the scaling criteria to satisfy thescaling threshold. In some such cases, the failure of a media agent maynot result in the remainder of the process 1000 being performed. But thefailure of additional media agents in the future that result in thescaling criteria satisfying the scaling threshold may cause theremainder of the process 1000 to be performed after the additional mediaagents have failed.

At block 1004, the storage manager 140 configures a computing system asa new media agent 144 or to include a new media agent 144. In someembodiments, the computing system may be configured as a secondarystorage computing device 106 that is configured to host or implement thenew media agent 144. In some cases, the secondary storage computingdevice 106 or the media agent 144 may be configured to replace asecondary storage computing device or a media agent that has failed. Inother cases, the secondary storage computing device 106 or the mediaagent 144 may be configured as a new or additional secondary storagecomputing device 106 or media agent 144.

At block 1006, the storage manager 140 restores the most recent backupindex 532 from the network storage system 302 to the new media agent 144to create a backup index 153 at the media agent 144. Restoring the mostrecent backup index may include retrieving the backup index from thenetwork store system 302 and storing it on an indexing system 502 of thenew secondary storage computing device 106. In some embodiments, thebackup index may be restored from the secondary storage device 108 atthe secondary storage system 118. The most recent backup index maycomprise the most recently created backup index generated and/or themost recently created backup index stored at the network storage system302. In some embodiments, the most recent backup index may be the mostrecent backup index identified as available or eligible for use orrestoration. For example, in some cases, one or more backup indexes maybe marked or identified as being expired, unavailable, corrupted, orotherwise unusable. In some such cases, the most recent backup index maybe marked as unavailable. In some cases, a most recent backup index maybe unusable because a more recent backup was discarded and an earlierbackup was identified as the most up-to-date backup to be used. Thus, insome cases, the most recent backup index restored at the block 1006 mayin fact not be the most recent backup index generated.

At block 1008, the storage manager 140 updates the backup index 153 atthe new media agent 144 based at least in part on one or moretransaction log files at the network storage system 302 that are morerecent than the backup index 153. The one or more transaction log filesmay be retrieved from the network storage system 302 and stored at theindexing system 502 of the new secondary storage computing device 106.In some embodiments, the one or more transaction log files may berestored from the secondary storage device 108 at the secondary storagesystem 118. In certain embodiments, the storage manager 140 accesses,retrieves, or cause to be retrieved one or more transaction log filesthat have a timestamp that is more recent than a timestamp associatedwith the backup index 153. In certain embodiments, at least some of thetransaction log files may be accessed from an indexing system of anothersecondary storage computing device. Further, in some cases, thetransaction log files may be stored at a distributed index, such as adistributed indexing system 502. Moreover, in certain embodiments, theremay be no transaction log files that are more recent than the backupindex. In such embodiments, the block 1008 may be omitted.

At decision block 1010, the storage manager 140 determines whether anytransaction identifiers that are more recent than the backup index 153exist. Determining whether any transaction identifiers that are morerecent than the backup index 153 exists may include comparing thetimestamp of the transaction identifiers with the timestamp of thebackup index and/or the one or more transaction log files used to updatethe backup index. The transaction identifiers may be accessed from anetwork storage system 302, from a secondary storage device 108, or froman indexing system 502 of another secondary storage computing device 106other than the one being replaced or added to the secondary storagesystem 118.

If it is determined at the decision block 1010 that there aretransaction identifiers that exist that are more recent than the backupindex 153, the storage manager 140, at block 1012, replays or causes tobe replayed transactions associated with the transaction identifiersthat are more recent than the backup index 153 to create an up-to-datebackup index. Replaying the transactions may include accessing one ormore transactions from transaction log files associated with thetransaction identifiers that have yet to be recorded in the backupindex. These one or more transactions may be replayed or performed andthe backup index may be updated to indicate that the transaction hasbeen flushed to backup. A flag in the backup index may indicate that thetransaction has been consumed to performed. By replaying thetransactions associated with the transaction identifiers, backup indexcan be updated to reflect the state of the index at a point in timewhere the media agent 144 of the block 1002 was detected to have failedor to the current state of the index. In certain embodiments, replayingthe transactions may be limited to replaying the effects of thetransactions on the index because, for example, although the index mayhave been lost when the media agent 144 failed, the backup of theprimary storage device associated with the index may still exist at thenetwork store system 302. In some embodiments, replaying thetransactions may include modifying the backup index 153 based on one ormore results generated by replaying the transactions. In someembodiments, one or more transaction identifiers are accessed from thenetwork storage manager 302. Alternatively, or in addition, one or moreof the transaction identifiers may be accessed from an indexing system502, which may be associated with another secondary storage computingdevice. In some cases the indexing system 502 may be a distributedindexing system that is distributed among a plurality of systems at thesecondary storage system 118.

After creating the up-to-date backup index at block 1012, or if it isdetermined that there are no transaction identifiers that are morerecent than the backup index at the decision block 1010, the storagemanager 140 adds the new media agent 144 to the set of available mediaagents at the secondary storage system 118. Adding the new media agent144 to the set of available media agents may include providing the newmedia agent with the up-to-date backup index. In some cases, providingthe up-to-date backup index to the new media agent 144 includes storingthe up-to-date backup index at an indexing system 502 of the new mediaagent 144. This indexing system 502 may be included as part of or hostedby the secondary storage computing device 106 that hosts the new mediaagent 144.

Further, adding the new media agent 144 to the set of available mediaagents may include identifying the new media agent 144 as available foruse by one or more client computing devices 102. Further, adding the newmedia agent 144 to the set of available media agents may include storingthe identity of or access information for the new media agent 144, orthe new secondary storage computing device 106, in the managementdatabase 146.

In certain embodiments, one or more of the blocks of the process 1000may be performed by the new media agent 144 itself. For example, afterthe storage manager 140 configures the secondary storage computingdevice 106 as a new media agent 144 or to include the media agent 144,the new media agent 144 may perform the operations associated with theblocks 1006, 1008, 1010, and 1012. Upon completion of the operationsassociated with the blocks 1010 and/or 1012, the new media agent 144 mayinform the storage manager 140 that the backup index has been restoredfor use by the new media agent 144 enabling the storage manager 142 atthe new media agent the set of available media agents as part of theblock 1014.

In regard to the figures described herein, other embodiments arepossible within the scope of the present invention, such that theabove-recited components, steps, blocks, operations, and/ormessages/requests/queries/instructions are differently arranged,sequenced, sub-divided, organized, and/or combined. In some embodiments,a different component may initiate or execute a given operation.

Example Use Cases

In one example use case, a backup of a client computing device 102, orother data management task, may be triggered. For example, a user mayrequest a backup or a scheduled backup time may be reached. The dataagent 142 may request a job ID and job metadata from a storage manager140 to perform the backup task using, for example the process 600. Thedata agent 142 may receive the job ID (e.g., Job ID XYZ) and jobmetadata indicating information to facilitate the backup process. Forexample, the job metadata may identify where to backup the data, howmany data connections to establish, or an amount of bandwidth availableto the client computing device 102. The job ID and job metadata may bestored at a job cache 516.

In embodiments where the client computing device 102 includes a coremedia agent 510, the data agent 142 may write or provide data from theprimary storage device 104 to the core media agent 510 for backup using,for example, the process 800. Metadata relating to the files to bebacked up may be provided to a data management system 506 at a mediaagent 144 or at an indexing agent 580 to create or maintain an index ofthe backup. In embodiments where the client computing device 102 doesnot include a core media agent 510, the data may be provided by the dataagent 142 to a media agent 144 at a secondary storage computing device106.

In a continuing example use case, a second job may be triggered. Forexample, an incremental backup may be triggered. The client computingdevice 102 may determine from the job cache that the job ID XYZ andassociated job metadata is still valid. For example, an associated timeto live value has not been reached or an invalidation commandinvalidating the job ID has not been received from the storage manager140. In such cases, the second job may be performed using the jobmetadata associated with the job ID XYZ. Thus, it may appear to thestorage manager 140 that the second job is a continuation of the firstjob. In other words, the client computing device 102 may cause one ormore other systems within the information management system 500 toassociate a plurality of jobs as one job under one job ID.Advantageously, overhead is reduced within the system 500 by reducingcommunication between systems within the system 500.

At some time subsequent to the performance of the first and second job,and possibly one or more additional jobs, the client computing device102 may provide a batch update to the storage manager 140 relating tothe plurality of jobs performed under the job ID XYZ. At such time, thestorage manager 140 may update a jobs agent 156 to identify theplurality of jobs performed under the job ID XYZ and whether the jobswere successful or failed.

Example Embodiments

Some example enumerated embodiments of the present invention are recitedin this section in the form of methods, systems, and non-transitorycomputer-readable media, without limitation.

One aspect of the disclosure provides a computer-implemented method ofmanaging a job at a client computing system of an information managementsystem. The computer-implemented method comprises: as implemented by adata agent within a client computing system comprising one or morehardware processors and configured with specific computer-executableinstructions, detecting a trigger to perform a job at a secondarystorage system; determining that an active job identifier does not existfor the client computing system; requesting a job identifier from astorage manager of an information management system; receiving the jobidentifier from the storage manager and a set of job metadata, whereinthe set of job metadata comprises an identity of resources available tothe client computing system to perform the job; storing the jobidentifier and the set of job metadata at a job cache of the clientcomputing system, wherein the job metadata is associated with the jobidentifier at the job cache; and performing the job at the secondarystorage system using at least some of the resources identified in theset of job metadata.

The method of the preceding paragraph can include any sub-combination ofthe following features: where the job comprises a backup job that backsup data from the client computing system to the secondary storage systemor a restore job that restores data from the secondary storage system tothe client computing system; where determining that the active jobidentifier does not exist comprises determining that an existing jobidentifier at the client computing device has expired; where determiningthat the active job identifier does not exist comprises determining thata threshold number of errors associated with an existing job identifierat the client computing device has occurred; where the method furthercomprises designating the job identifier as expired when determiningthat the threshold number of errors associated with the existing jobidentifier have occurred; where the information management systemcomprises the client computing system and the secondary storage system;where the resources identified by the job metadata comprise one or moreof filters that filter data to include as part of the job; a number ofcommunication streams available for use by the client computing systemto communicate with the secondary storage system; an identity of one ormore secondary storage devices of the secondary storage system availableto the client computing system; or one or more file scanning resourcesavailable to the client computing system; where performing the job atthe secondary storage system comprises: storing data at a networkstorage system that is external to the information management systemwithout communicating with a media agent of the secondary storagesystem; and providing index information associated with the data to themedia agent of the secondary storage system; where the method furthercomprises: detecting a trigger to perform a second job at the secondarystorage system; determining that the job identifier stored at the jobcache remains active; accessing the job cache to determine the set ofjob metadata associated with the job identifier; and performing thesecond job at the secondary storage system using at least some of theresources identified in the set of job metadata without accessing thestorage manager; where the method further comprises associating aplurality of jobs with the job identifier at the client computingsystem; where the storage manager is unaware of at least one job fromthe plurality of jobs associated with the job identifier for at least aperiod of time; where performing a batch update with respect to thestorage manager, wherein the batch update comprises providing thestorage manager at least a unique identifier of each job of theplurality of jobs associated with the job identifier; where the methodfurther comprises receiving an updated set of job metadata associatedwith the job identifier from the storage manager; and updating the jobmetadata stored at the job cache based at least in part on the updatedset of job metadata; and where the trigger comprises one or more of ascheduled job, a command, or a threshold amount of new or modified dataat a primary storage of the client computing system.

Another aspect of the disclosure provides a system for managing a job ata client computing system of an information management system. Thesystem comprises a data agent of a client computing system comprisingone or more hardware processors. The data agent may be configured to:detect a trigger to perform a job at a secondary storage system;determine that an active job identifier does not exist for the clientcomputing system; request a job identifier from a storage manager of aninformation management system; receive the job identifier from thestorage manager and a set of job metadata; store the job identifier andthe set of job metadata at a job cache; and perform the job at thesecondary storage system based at least in part on the set of jobmetadata.

The system of the preceding paragraph can include any sub-combination ofthe following features: where the data agent is further configured todetermine that a threshold number of errors associated with the anexisting job identifier at the client computing device has occurred; anddesignate the existing job identifier as unusable; where the secondarystorage comprises one or more secondary storage devices and a networkstorage system; where the data agent is further configured to performthe job at the secondary storage system by: storing data at a networkstorage system without communicating with a media agent of the secondarystorage system; and providing index information associated with the datato the media agent of the secondary storage system; where the data agentis further configured to: detect a trigger to perform a second job atthe secondary storage system; determine that the job identifier storedat the job cache remains active; access the job cache to obtain the setof job metadata associated with the job identifier; and perform thesecond job at the secondary storage system using at least some of theresources identified in the set of job metadata without accessing thestorage manager; and where the data agent is further configured to:receive an updated set of job metadata associated with the jobidentifier from the storage manager; and update the job metadata storedat the job cache based at least in part on the updated set of jobmetadata.

Another aspect of the disclosure provides a computer-implemented methodof backing up a client computing system of an information managementsystem. The computer implemented method comprises: as implemented by adata agent within a client computing system comprising one or morehardware processors and configured with specific computer-executableinstructions, detecting a trigger to perform an instance of a backupprocess at a network storage system during a first time period;determining that the client computing system is capable of interactingwith the network storage system during the first time period; backing updata from a primary storage of the client computing system using a coremedia agent at the client computing system as part of the instance ofthe backup process, wherein the data is backed up to the network storagesystem without accessing a media agent at a secondary storage system ofthe information management system; and providing backup metadata to themedia agent at the secondary storage system without providing the datafrom the primary storage to the media agent.

The method of the preceding paragraph can include any sub-combination ofthe following features: where the method further comprises: accessing ajob cache to obtain job metadata; and determining based at least in parton the job metadata that the client computing system is capable ofinteracting with the network storage system; where the job metadatacomprises access information for accessing the network storage system;where determining that the client computing system is capable ofinteracting with the network storage system comprises communicating atest packet to the network storage system; where determining that theclient computing system is capable of interacting with the networkstorage system comprises determining that the client computing system iscapable of interacting with the network storage system directly or viaan external network without communicating with an intermediary system ofthe information management system; where the network storage system isexternal to the information management system; where the method furthercomprises detecting a trigger to perform a second instance of the backupprocess at the network storage system during a second time period thatdiffers from the first time period; determining that the clientcomputing system is not capable of interacting with the network storagesystem during the second time period; and providing data from theprimary storage of the client computing system for backup as part of thesecond instance of the backup process to the media agent at thesecondary storage system; where determining that the client computingsystem is not capable of interacting with the network storage systemduring the second time period comprises determining that the clientcomputing system is not capable of providing data for backup to thenetwork storage system without providing the data to the media agent atthe secondary storage system; where the trigger comprises one or more ofa scheduled backup, a command, or a threshold amount of new or modifieddata at the primary storage of the client computing system; where themethod further comprises detecting a trigger to perform an instance of arestore process to restore data from the network storage system;retrieving a backup index from the media agent at the secondary storagesystem, the backup index created based at least in part on the backupmetadata; and restoring, using the core media agent, the data from thenetwork storage system based at least in part on the backup indexwithout accessing the media agent to obtain the data when it isdetermined that the client computing system is capable of interactingwith the network storage system during a restore time period; where themethod further comprises restoring, using the media agent, the data fromthe network storage system based at least in part on the backup index toobtain the data when it is determined that the client computing systemis not capable of interacting with the network storage system during therestore time period; and where backing up the data from the primarystorage using the core media agent comprises writing the data to amemory space of the core media agent, wherein the core media agentprovides the data written to the memory space of the core media agent tothe network storage system for backup.

Another aspect of the disclosure provides a system for backing up aclient computing system of an information management system. The systemcomprises a data agent of a client computing system comprising one ormore hardware processors. The data agent may be configured to: detect atrigger to perform an instance of a backup process at a network storagesystem during a first time period; determine that the client computingsystem is capable of interacting with the network storage system duringthe first time period; back up data from a primary storage of the clientcomputing system using a core media agent at the client computing systemas part of the instance of the backup process, wherein the data isbacked up to the network storage system without accessing a media agentat a secondary storage system of the information management system; andprovide backup metadata to the media agent at the secondary storagesystem without providing the data from the primary storage to the mediaagent.

The system of the preceding paragraph can include any sub-combination ofthe following features: where the data agent is further configured to:access a job cache to obtain job metadata; and determine based at leastin part on the job metadata that the client computing system is capableof interacting with the network storage system; where the job metadatacomprises access information for accessing the network storage system;where the data agent is further configured to: detect a trigger toperform a second instance of the backup process at the network storagesystem during a second time period that differs from the first timeperiod; determine that the client computing system is not capable ofinteracting with the network storage system during the second timeperiod; and provide data from the primary storage of the clientcomputing system for backup as part of the second instance of the backupprocess to the media agent at the secondary storage system; wheredetermining that the client computing system is not capable ofinteracting with the network storage system during the second timeperiod comprises determining that the client computing system is notcapable of providing data for backup to the network storage systemwithout providing the data to the media agent at the secondary storagesystem; where the data agent is further configured to: detect a triggerto perform an instance of a restore process to restore data from thenetwork storage system; retrieve a backup index from the media agent atthe secondary storage system, the backup index created based at least inpart on the backup metadata; and use the core media agent to restore thedata from the network storage system based at least in part on thebackup index without accessing the media agent to obtain the data whenit is determined that the client computing system is capable ofinteracting with the network storage system during a restore timeperiod; where the data agent is further configured to use the mediaagent to restore the data from the network storage system based at leastin part on the backup index when it is determined that the clientcomputing system is not capable of interacting with the network storagesystem during the restore time period; and where the data agent isfurther configured to back up the data from the primary storage usingthe core media agent by writing the data to a memory space of the coremedia agent enabling the core media agent to access the data for backupto the network storage system.

Another aspect of the disclosure provides a computer-implemented methodof a multi-tiered backup indexing process of an information managementsystem. The computer implemented method comprises: as implemented by amedia agent within a secondary storage computing device comprising oneor more hardware processors and configured with specificcomputer-executable instructions, receiving backup metadata from aclient computing system undergoing a backup process at a first timeperiod; generating a backup index based at least in part on the receivedbackup metadata; receiving job metadata corresponding to a job performedwith respect to the client computing system at a second time period;generating a transaction log file based on the job metadata, wherein thetransaction log file comprises a reduced set of metadata compared to thebackup metadata used to generate the backup index enabling fasterprocessing of the transaction log file than the backup index; andupdating the backup index based at least in part on the transaction logfile at a period of time that occurs after completion of the jobperformed at the second time period.

The method of the preceding paragraph can include any sub-combination ofthe following features: where the method further comprises: where thebackup index comprises a full index associated with a full backup of theclient computing system; where the backup index comprises a distributedindex that is distributed across a plurality of media agents across aplurality of secondary storage computing devices; where the reduced setof metadata comprises file attributes of files undergoing the jobperformed with respect to the client computing system at the second timeperiod; where the job performed with respect to the client computingsystem at the second time period comprises a backup job; where thebackup job comprises one or more of a differential backup, a partialbackup, a reduced backup, an archive operation, or a non-full backup;where the method further comprises storing one or more transactionidentifiers of one or more transactions occurring subsequent togenerating the transaction log file; where the method further comprisesgenerating a second transaction log file at a third time period based atleast in part on the one or more transaction identifiers for the one ormore transactions occurring subsequent to generating the transaction logfile; where the method further comprises discarding the one or moretransaction identifiers after generating the second transaction log;where the method further comprises backing up the backup index and thetransaction log file to a network storage system; where the backup indexor the transaction log file is backed up at a different time period thandata of a primary storage of a client computing system being backed upas part of the backup process; where updating the backup index comprisesgenerating a new copy of the backup index that is updated based at leastin part on the transaction log file; where generating the transactionlog file based on the job metadata comprises generating a plurality oftransaction log files based on the job metadata as the job metadata isreceived over a period of time associated with the second time period;and where the method further comprises storing the backup index and thetransaction log file at an indexing system of a secondary storagesystem, the secondary storage system including the secondary storagecomputing device.

Another aspect of the disclosure provides a system for performing amulti-tiered backup indexing process of an information managementsystem. The system comprises: a media agent of a secondary storagecomputing device comprising one or more hardware processors, the mediaagent configured to: receive backup metadata from a client computingsystem undergoing a backup process at a first time period; generate abackup index based at least in part on the received backup metadata;receive job metadata corresponding to a job performed with respect tothe client computing system at a second time period; generate atransaction log file based on the job metadata, wherein the transactionlog file comprises a reduced set of metadata compared to the backupmetadata used to generate the backup index enabling faster processing ofthe transaction log file than the backup index; and update the backupindex based at least in part on the transaction log file at a period oftime that occurs after completion of the job performed at the secondtime period.

The system of the preceding paragraph can include any sub-combination ofthe following features: where the media agent is further configured tostore one or more transaction identifiers of one or more transactionsoccurring subsequent to generating the transaction log file; where themedia agent is further configured to generate a second transaction logfile at a third time period based at least in part on the one or moretransaction identifiers for the one or more transactions occurringsubsequent to generating the transaction log file; where the media agentis further configured to periodically backup, at a network storagesystem, backup indexes and transaction log files, wherein the backupindexes include the backup index and the transaction log files includethe transaction log file; where data that is backed up as part of thebackup process is backed up during a different period of time than thebackup index generated based at least in part on the received backupmetadata, wherein the backup index corresponds to the data that isbacked up; and where the media agent is further configured to replicatethe backup index across a plurality of media agents.

Another aspect of the disclosure provides a computer-implemented methodof configuring a media agent of an information management system. Thecomputer-implemented method comprising: as implemented by a storagemanager within an information management system, the storage managercomprising one or more hardware processors and configured with specificcomputer-executable instructions, configuring a secondary computingsystem as a media agent; restoring a backup index from a network storagesystem to the media agent; accessing a transaction log file at thenetwork storage system that is more recent than the backup index;updating the backup index at the media agent based at least in part onthe transaction log file to obtain a current backup index; associatingthe current backup index with the media agent; and adding the mediaagent to a set of available media agents at a secondary storage systemof the information management system.

The method of the preceding paragraph can include any sub-combination ofthe following features: where configuring the secondary computing systemas the media agent comprises configuring the secondary computing systemto host the media agent; where the secondary computing system comprisesa computing system at the secondary storage system of the informationmanagement system; where the method further comprises detecting afailure of a second media agent that differs from the media agent,wherein configuring the secondary computing system as the media agentoccurs in response to detecting the failure of the second media agent;where the failure of the second media agent comprises a loss of accessto the second media agent; where the backup index is one of a pluralityof backup indexes at the network storage system, and wherein the backupindex is the most recently generated backup index of the plurality ofbackup indexes; where the transaction log file is associated with atimestamp that is more recent than a timestamp of the backup index;where the transaction log file comprises a set of file attributes forone or more files that have been backed up during a period of time thatis more recent than when the backup index was generated; where thetransaction log file is one of a plurality of transaction log files,wherein each transaction log file is generated at a different timeperiod, and wherein each transaction log file is more recent than thebackup index; where adding the media agent to the set of available mediaagents comprises designating the media agent as available for use by aprimary storage system in a management repository of the storagemanager; wherein the method further comprises accessing a transactionidentifier that is more recent than the transaction log file; andupdating the current backup index based at least in part on thetransaction identifier to obtain an updated current backup index,wherein associating the current backup index with the media agentcomprises associating the updated current backup index with the mediaagent; where updating the current backup index based at least in part onthe transaction identifier comprises replaying a transaction associatedwith the transaction identifier and updating the current backup indexbased on a result of replaying the transaction; and where thetransaction identifier is accessed from a distributed indexing system.

Another aspect of the disclosure provides a system for configuring amedia agent at an information management system. The system comprises: astorage manager comprising one or more hardware processors, the storagemanager configured to: configure a secondary computing system as a mediaagent; restore a backup index from a network storage system to the mediaagent; access a transaction log file at the network storage system thatis more recent than the backup index; update the backup index at themedia agent based at least in part on the transaction log file to obtaina current backup index; provide the media agent with access to thecurrent backup index; and add the media agent to a set of availablemedia agents at a secondary storage system of the information managementsystem.

The system of the preceding paragraph can include any sub-combination ofthe following features: where the storage manager is further configuredto determine that a scaling criteria satisfies a scaling threshold,wherein configuring the secondary computing system as the media agentoccurs in response to detecting that the scaling criteria satisfies thescaling threshold; where the storage manager is further configured toadd the media agent to the set of available media agents by replacing asecond media agent of the set of available media agents with the mediaagent; where the transaction log file comprises a reduced set ofmetadata for a backed up file compared to the backup index; where thestorage manager is further configured to add the media agent to the setof available media agents by designating the media agent as availablefor use in a management repository of the storage manager; where thestorage manager is further configured to: access a transactionidentifier that is associated with a timestamp that is more recent thana timestamp of the transaction log file; and update the current backupindex based at least in part on the transaction identifier to obtain anupdated current backup index, wherein providing the media agent withaccess to the current backup index comprises providing the media agentwith access to the updated current backup index with the media agent;and where the storage manager is further configured to update thecurrent backup index based at least in part on the transactionidentifier by replaying a transaction associated with the transactionidentifier and updating the current backup index based on a result ofreplaying the transaction.

In other embodiments, a system or systems may operate according to oneor more of the methods and/or computer-readable media recited in thepreceding paragraphs. In yet other embodiments, a method or methods mayoperate according to one or more of the systems and/or computer-readablemedia recited in the preceding paragraphs. In yet more embodiments, acomputer-readable medium or media, excluding transitory propagatingsignals, may cause one or more computing devices having one or moreprocessors and non-transitory computer-readable memory to operateaccording to one or more of the systems and/or methods recited in thepreceding paragraphs.

Terminology

Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainembodiments include, while other embodiments do not include, certainfeatures, elements and/or steps. Thus, such conditional language is notgenerally intended to imply that features, elements and/or steps are inany way required for one or more embodiments or that one or moreembodiments necessarily include logic for deciding, with or without userinput or prompting, whether these features, elements and/or steps areincluded or are to be performed in any particular embodiment.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense, as opposed to anexclusive or exhaustive sense, i.e., in the sense of “including, but notlimited to.” As used herein, the terms “connected,” “coupled,” or anyvariant thereof means any connection or coupling, either direct orindirect, between two or more elements; the coupling or connectionbetween the elements can be physical, logical, or a combination thereof.Additionally, the words “herein,” “above,” “below,” and words of similarimport, when used in this application, refer to this application as awhole and not to any particular portions of this application. Where thecontext permits, words using the singular or plural number may alsoinclude the plural or singular number respectively. The word “or” inreference to a list of two or more items, covers all of the followinginterpretations of the word: any one of the items in the list, all ofthe items in the list, and any combination of the items in the list.Likewise the term “and/or” in reference to a list of two or more items,covers all of the following interpretations of the word: any one of theitems in the list, all of the items in the list, and any combination ofthe items in the list.

In some embodiments, certain operations, acts, events, or functions ofany of the algorithms described herein can be performed in a differentsequence, can be added, merged, or left out altogether (e.g., not allare necessary for the practice of the algorithms). In certainembodiments, operations, acts, functions, or events can be performedconcurrently, e.g., through multi-threaded processing, interruptprocessing, or multiple processors or processor cores or on otherparallel architectures, rather than sequentially.

Systems and modules described herein may comprise software, firmware,hardware, or any combination(s) of software, firmware, or hardwaresuitable for the purposes described. Software and other modules mayreside and execute on servers, workstations, personal computers,computerized tablets, PDAs, and other computing devices suitable for thepurposes described herein. Software and other modules may be accessiblevia local computer memory, via a network, via a browser, or via othermeans suitable for the purposes described herein. Data structuresdescribed herein may comprise computer files, variables, programmingarrays, programming structures, or any electronic information storageschemes or methods, or any combinations thereof, suitable for thepurposes described herein. User interface elements described herein maycomprise elements from graphical user interfaces, interactive voiceresponse, command line interfaces, and other suitable interfaces.

Further, processing of the various components of the illustrated systemscan be distributed across multiple machines, networks, and othercomputing resources. Two or more components of a system can be combinedinto fewer components. Various components of the illustrated systems canbe implemented in one or more virtual machines, rather than in dedicatedcomputer hardware systems and/or computing devices. Likewise, the datarepositories shown can represent physical and/or logical data storage,including, e.g., storage area networks or other distributed storagesystems. Moreover, in some embodiments the connections between thecomponents shown represent possible paths of data flow, rather thanactual connections between hardware. While some examples of possibleconnections are shown, any of the subset of the components shown cancommunicate with any other subset of components in variousimplementations.

Embodiments are also described above with reference to flow chartillustrations and/or block diagrams of methods, apparatus (systems) andcomputer program products. Each block of the flow chart illustrationsand/or block diagrams, and combinations of blocks in the flow chartillustrations and/or block diagrams, may be implemented by computerprogram instructions. Such instructions may be provided to a processorof a general purpose computer, special purpose computer,specially-equipped computer (e.g., comprising a high-performancedatabase server, a graphics subsystem, etc.) or other programmable dataprocessing apparatus to produce a machine, such that the instructions,which execute via the processor(s) of the computer or other programmabledata processing apparatus, create means for implementing the actsspecified in the flow chart and/or block diagram block or blocks. Thesecomputer program instructions may also be stored in a non-transitorycomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to operate in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meanswhich implement the acts specified in the flow chart and/or blockdiagram block or blocks. The computer program instructions may also beloaded to a computing device or other programmable data processingapparatus to cause operations to be performed on the computing device orother programmable apparatus to produce a computer implemented processsuch that the instructions which execute on the computing device orother programmable apparatus provide steps for implementing the actsspecified in the flow chart and/or block diagram block or blocks.

Any patents and applications and other references noted above, includingany that may be listed in accompanying filing papers, are incorporatedherein by reference. Aspects of the invention can be modified, ifnecessary, to employ the systems, functions, and concepts of the variousreferences described above to provide yet further implementations of theinvention. These and other changes can be made to the invention in lightof the above Detailed Description. While the above description describescertain examples of the invention, and describes the best modecontemplated, no matter how detailed the above appears in text, theinvention can be practiced in many ways. Details of the system may varyconsiderably in its specific implementation, while still beingencompassed by the invention disclosed herein. As noted above,particular terminology used when describing certain features or aspectsof the invention should not be taken to imply that the terminology isbeing redefined herein to be restricted to any specific characteristics,features, or aspects of the invention with which that terminology isassociated. In general, the terms used in the following claims shouldnot be construed to limit the invention to the specific examplesdisclosed in the specification, unless the above Detailed Descriptionsection explicitly defines such terms. Accordingly, the actual scope ofthe invention encompasses not only the disclosed examples, but also allequivalent ways of practicing or implementing the invention under theclaims.

To reduce the number of claims, certain aspects of the invention arepresented below in certain claim forms, but the applicant contemplatesother aspects of the invention in any number of claim forms. Forexample, while only one aspect of the invention is recited as ameans-plus-function claim under 35 U.S.C sec. 112(f) (AIA), otheraspects may likewise be embodied as a means-plus-function claim, or inother forms, such as being embodied in a computer-readable medium. Anyclaims intended to be treated under 35 U.S.C. § 112(f) will begin withthe words “means for,” but use of the term “for” in any other context isnot intended to invoke treatment under 35 U.S.C. § 112(f). Accordingly,the applicant reserves the right to pursue additional claims afterfiling this application, in either this application or in a continuingapplication.

What is claimed is:
 1. A computer-implemented method of backing up aclient computing system of an information management system, thecomputer-implemented method comprising: as implemented by a data agentwithin a client computing system comprising one or more hardwareprocessors and configured with specific computer-executableinstructions, detecting a trigger to perform an instance of a backupprocess at a network storage system during a first time period;determining that the client computing system is capable of interactingwith the network storage system during the first time period; backing updata from a primary storage of the client computing system using a coremedia agent at the client computing system as part of the instance ofthe backup process, wherein the data is backed up to the network storagesystem without accessing a media agent at a secondary storage system ofthe information management system; and providing backup metadata to themedia agent at the secondary storage system without providing the datafrom the primary storage to the media agent.